wipfeat: no-std support #86
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
tbh I'm not exactly sure this will be useful at all, but I encountered this while looking into converting more reth crates to no-std, so I looked into it for a bit.
this currently still fails because alloy-rlp is still on msrv 1.64 before Ip-net types were moved to core.
we can work around this by introducing a separate feature for this on alloy-rlp (alloy-rs/rlp#30).
I couldn't find a msrv, using
core::error::Errorwould require msrv 1.81, alternatively this could likely be feature gated.totally fine if no-std is not planned or even useful, I assume k256 could work though