Skip to content

Minor wording updates to the undefined behavior section #14

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jan 15, 2025
Merged

Minor wording updates to the undefined behavior section #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/undefined_behavior.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,9 +159,9 @@ arrangement of safe code can cause undefined behavior. That's a lot to consider!
The "safety conditions" for unsafe traits and functions are just the conditions
under which it does not trigger undefined behavior. These conditions aren't
checked by the compiler, they're checked by the people who write the code
itself. Therefore, unsafe blocks must be manually checked to verify that the
code written upholds all of the conditions required to avoid undefined behavior.
Any unsafe code that can trigger undefined behavior _even when its safety
itself. Therefore, unsafe impls and blocks must be manually checked to verify
that the code written upholds all of the conditions required to avoid undefined
behavior. Any unsafe code that can trigger undefined behavior _when its safety
conditions are upheld_ is unsound.


Expand Down
Loading