Is there an existing issue for this?
Current Behavior
Current patina has default feature include 'alloc'. This will cause any crate that tries to use patina to enable alloc feature and impose a requirement of global_allocator for the built module.
--no-default-features will not help because it only applied to the top level config.
Expected Behavior
alloc should be enabled on demand and the change should not be breaking.
Steps To Reproduce
Do a binary build without supplying neither the global_allocator nor the alloc feature flag, the build will break for any given crate that pulls in patina sdk.
Build Environment
- OS(s): Windows
- Tool Chain(s): cargo nightly 2026-02-06
- Targets Impacted: aarch64 and x64
Version Information
Urgency
Medium
Are you going to fix this?
I will fix it
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response
Is there an existing issue for this?
Current Behavior
Current patina has default feature include 'alloc'. This will cause any crate that tries to use patina to enable
allocfeature and impose a requirement of global_allocator for the built module.--no-default-featureswill not help because it only applied to the top level config.Expected Behavior
alloc should be enabled on demand and the change should not be breaking.
Steps To Reproduce
Do a binary build without supplying neither the global_allocator nor the alloc feature flag, the build will break for any given crate that pulls in patina sdk.
Build Environment
Version Information
Urgency
Medium
Are you going to fix this?
I will fix it
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response