Add safety preconditions to alloc/src/boxed/thin.rs#119
Draft
tautschnig wants to merge 9 commits intomodel-checking:mainfrom
Draft
Add safety preconditions to alloc/src/boxed/thin.rs#119tautschnig wants to merge 9 commits intomodel-checking:mainfrom
tautschnig wants to merge 9 commits intomodel-checking:mainfrom
Conversation
Note that I've added `#[requires]` attributes to represent the safety conditions as code contracts. These are based on the "SAFETY:" comments in the original code. The conditions are: 1. For `with_header`, we require that the pointer is aligned. 2. For `drop`, we require that the value pointer is either null or aligned. 3. For `header`, we require that the pointer is aligned. These contracts ensure that the safety conditions mentioned in the comments are checked at compile-time or runtime, depending on the contract system used.
tautschnig
force-pushed
the
bedrock-library/alloc/src/boxed/thin.rs
branch
from
32efecb to
bb44f4b
Compare
Just as previously done for core: this will enable future use of
`safety::{ensures,requires}` in those crates.
These have SAFETY comments explaining why their `unsafe` sections are indeed safe, but the overall function should be safe for all inputs.
celinval
reviewed
Oct 17, 2024
| // Safety: | ||
| // - Assumes that either `value` can be dereferenced, or is the | ||
| // `NonNull::dangling()` we use when both `T` and `H` are ZSTs. | ||
| #[requires((mem::size_of_val_raw(value) == 0 && size_of::<H>() == 0) || |
There was a problem hiding this comment.
We're still missing the safety of self for type T.
…/src/boxed/thin.rs
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Note that I've added
#[requires]attributes to represent the safety conditions as code contracts. These are based on the "SAFETY:" comments in the original code. The conditions are:with_header, we require that the pointer is aligned.drop, we require that the value pointer is either null or aligned.header, we require that the pointer is aligned.These contracts ensure that the safety conditions mentioned in the comments are checked at compile-time or runtime, depending on the contract system used.