Add MaybeUninit type
#319
Closed
Add MaybeUninit type
#319
Conversation
This file contains 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
Closed
joshlf
force-pushed
the
try-from-bytes-minimal-1-maybe-uninit
branch
2 times, most recently
from
7ba4acc
to
c7b2773
Compare
joshlf
force-pushed
the
try-from-bytes-minimal-1-maybe-uninit
branch
2 times, most recently
from
0fd6067
to
d5f7888
Compare
joshlf
force-pushed
the
known-layout-3-ref-raw-pointer
branch
from
9bc0c28
to
cf25d48
Compare
joshlf
force-pushed
the
try-from-bytes-minimal-1-maybe-uninit
branch
from
d5f7888
to
fd7dcba
Compare
joshlf
force-pushed
the
known-layout-3-ref-raw-pointer
branch
from
cf25d48
to
a17bec7
Compare
joshlf
force-pushed
the
try-from-bytes-minimal-1-maybe-uninit
branch
from
fd7dcba
to
39d24ff
Compare
joshlf
force-pushed
the
known-layout-3-ref-raw-pointer
branch
from
a17bec7
to
1d52c41
Compare
joshlf
force-pushed
the
try-from-bytes-minimal-1-maybe-uninit
branch
2 times, most recently
from
62b67f7
to
2ad98f3
Compare
joshlf
changed the base branch from
known-layout-3-ref-raw-pointer
to
known-layout-2-known-layout
joshlf
force-pushed
the
try-from-bytes-minimal-1-maybe-uninit
branch
2 times, most recently
from
430cade
to
557dac0
Compare
joshlf
force-pushed
the
known-layout-2-known-layout
branch
from
87c2b56
to
6de0dfd
Compare
joshlf
force-pushed
the
try-from-bytes-minimal-1-maybe-uninit
branch
from
557dac0
to
7ddaeb4
Compare
joshlf
force-pushed
the
known-layout-2-known-layout
branch
from
6de0dfd
to
c0713db
Compare
joshlf
force-pushed
the
try-from-bytes-minimal-1-maybe-uninit
branch
from
7ddaeb4
to
fabeea2
Compare
The standard library's `MaybeUninit` type does not currently support wrapping unsized types. This commit introduces a polyfill with the same behavior as `MaybeUninit` which does support wrapping unsized types. In this commit, the only supported types are sized types and slice types. Later (as part of #29), we will add the ability to derive the `AsMaybeUninit` trait, which will extend support to custom DSTs. TODO: Figure out how to get rid of KnownLayout<MaybeUninit = mem::MaybeUninit<T>> bounds. Makes progress on #29
joshlf
force-pushed
the
known-layout-2-known-layout
branch
from
c0713db
to
b0735fc
Compare
joshlf
force-pushed
the
try-from-bytes-minimal-1-maybe-uninit
branch
from
fabeea2
to
3113e26
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The standard library's
MaybeUninittype does not currently support wrapping unsized types. This commit introduces a polyfill with the same behavior asMaybeUninitwhich does support wrapping unsized types.In this commit, the only supported types are sized types and slice types. Later (as part of #29), we will add the ability to derive the
AsMaybeUninittrait, which will extend support to custom DSTs.Makes progress on #29