Skip to content

Conversation

@pinkforest
Copy link
Contributor

@pinkforest pinkforest commented Jan 19, 2026

Ref:

In preparation for no-alloc RSA we would need gating alloc to default-on alloc feature.

Anyone using this in no_std context with default-features == false needs to add alloc feature given the current impl is alloc.

But on top if this we can start adding generic no-alloc impl without breaking the current alloc-dependant impl.

I could start trying with FixedPrivateKey etc. on next PR and then we can generalize actual algos around that and alloc one without breakage.

Also need to add the alloc gating into crypto-primes and / or just avoid keygen for no-alloc to start.

@tarcieri
Copy link
Member

I think something like this will make more sense when there's some level of baseline no_alloc functionality in-place, but right now we don't have any so gating everything like this will just leave an empty crate if you shut the alloc feature off

@pinkforest
Copy link
Contributor Author

yea true. I'll leave this as WIP as it's required anyways for testing no-alloc impls and seeing what needs to get done.

anyone wanting to join the effort can just PR my branch

@pinkforest pinkforest changed the title Gate alloc default-on WIP: no-alloc Jan 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants