-
Notifications
You must be signed in to change notification settings - Fork 238
implement Write for uninitialized slices #674
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
Open
master-hax
wants to merge
6
commits into
rust-embedded:master
Choose a base branch
from
master-hax:uninit
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 5 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
fdec431
support writing to uninit slices
master-hax 3478e99
use split_at consistently
master-hax e5d2e2d
update documentation
master-hax ef7758b
doc nit
master-hax dd98ad6
cargo fmt
master-hax 00346c9
use core::ptr::copy_nonoverlapping as suggested
master-hax File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
maybe core::ptr::copy_nonoverlapping has a better chance at getting optimized than iterator loops. Or maybe copy_from_slice but i'm not sure if it's possible to use soundly.
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.
also
buf.split_at(amt).0
can be written more readably asbuf[..amt]
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.
agreed, but that requires unsafe code. perhaps we could add that under a feature flag in a future PR?
they behave differently though -
.split_at()
splits the lifetime and also works inconst
contexts, so i think it is preferred over slicing with[]
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.
that's not a problem
the lifetime is not an issue with readonly
&[u8]
because aliasing is allowed, and slicing is also allowed in const.Uh oh!
There was an error while loading. Please reload this page.
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.
from what i can tell, slicing is not allowed in const contexts.
this example
main.rs
using.split_at(n).0
compiles just fine:whereas this example
main.rs
using[..n]
fails to compile:so i think because it supports const contexts, "shrinks" the lifetime, and provides a more simple API,
split_at()
should be preferred. fwiw i actually like the readability after getting used to it. i had to deal withconst
issues earlier while working in another no_std crate mmstick/numtoa#23Uh oh!
There was an error while loading. Please reload this page.
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.
updated to replace safe iterator with unsafe
core::ptr::copy_nonoverlapping
in 00346c9