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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
enforce
no_std
for all? protocol/v2 crates #1230enforce
no_std
for all? protocol/v2 crates #1230Changes from all commits
58c53c0
133f73e
433d9cb
76670d9
83d07c0
1a9012a
537a6ac
b4da137
8cd634b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can now use
#![no_std]
, and I'm confident that we are not using anystd
-compliant methods inbinary_codec_sv2
in any of the top-level crates that depend on it. Since almost all of our crates areno_std
-compliant, makes sense to have no-serde-sv2 to no-std only. cc: @rrybarczykThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I asked about this in this comment.
Current
binary_codec_sv2
has a brokenstd
support, do we want to remove it or fix it ?Look like you propose to remove it. It is also my preference.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also think we should enforce
no_std
on theprotocols
crates. So let's remove.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR looks good to me and is ready to go. We can enforce the
no-std
restriction during our protocol refactoring effort, once we have more concrete reasoning for removingstd
-related imports. However, I’m fine with either approach.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree. Let's confirm in the dev meet before we approve.
Check warning on line 687 in utils/buffer/src/buffer_pool/mod.rs
Codecov / codecov/patch
utils/buffer/src/buffer_pool/mod.rs#L687