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
Use/require byte equality in VarZeroVec #1103
Use/require byte equality in VarZeroVec #1103
Changes from 4 commits
07c15d8
2db8348
8b69d47
f27a588
419a0bb
0a8162d
adcab75
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.
Please add a default impl for
from_byte_slice_unchecked
as well. For ULE, you can usemem::size_of
to figure out how long to make the resulting slice. For VarULE, I think you can just cast it, right?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.
You can't cast it for VarULE because there's no way to generically do the inverse operation of
size_of_val()
("I have X bytes, tell me what the pointer metadata should be"). For example, consider what would happen with stuff likestruct ComplexULE(u8, char::ULE, [u32::ULE])
, calculating the pointer metadata for that is very specific to that type.Now fortunately the only kind of DST we can theoretically support are slice DSTs and compound slice DSTs, but just to give an example of why the inverse of
size_of_val()
is untractable: how woudl you solve that for trait objects? At least for compound slice-based DSTs rustc could theoretically add APIs tostd::ptr::metadata
that let you do this.