Rename NoCell to Immutable
#1137
Merged
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
We selected `Immutable` on @rcoh's suggestion that our name for this be a single, evocative word, like `Send` and `Sync`. As with `Send` and `Sync`, we do not hope that `Immutable`, on its own, captures the entire semantics of this trait; the burden of entirely capturing its semantics rests on its documentation. We are not overly concerned with the risk of future conflict with Rust. If and when Rust stabilizes its own version of this trait, we will adjust zerocopy to use Rust's trait instead. Closes #994
joshlf
approved these changes
Apr 24, 2024
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.
We selected
Immutableon @rcoh's suggestion that our name for this be a single, evocative word, likeSendandSync. As withSendandSync, we do not hope thatImmutable, on its own, captures the entire semantics of this trait; the burden of entirely capturing its semantics rests on its documentation.We are not overly concerned with the risk of future conflict with Rust. If and when Rust stabilizes its own version of this trait, we will adjust zerocopy to use Rust's trait instead.
Closes #994