Skip to content

Conversation

@mkatychev
Copy link

Added support, through use of extern crate alloc;, for no_std targets.

  • added std feature flag
  • bumped crate edition to 2024
  • bumped minor version

Comment on lines -58 to -61
#[cfg(all(feature = "ring", feature = "pure_rust"))]
compile_error!(
"ecies-rd25519: Feature 'ring' and 'pure_rust' cannot both be enabled. Please choose one."
);
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having an XOR feature set will cause issues for downstream users:
https://doc.rust-lang.org/cargo/reference/features.html#feature-unification

@mkatychev
Copy link
Author

@phayes I'm happy to revert 6b6f550 if need be
But I think the benefits of running cargo build --no-default-features (thus maintaining additive featureset guarantees) outweigh pulling in additional dependencies.

cargo tree --no-default-features --features ring does show that it pulls in aes-gcm, sha2, digest, and hkdf as dependencies but it should not impact the rlib size as by default LLVM (and almost all backends) optimizes out any unused functions.

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.

1 participant