Skip to content

Define sound and unsound #647

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
Centril merged 4 commits into from
Aug 6, 2019
Merged

Define sound and unsound #647

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3724dab
sound and unsound
RalfJung Aug 5, 2019
1ef61c3
Apply suggestions from code review
RalfJung Aug 6, 2019
95995e5
no excuse
RalfJung Aug 6, 2019
3597e8f
quantifying more explicitly over all clients
RalfJung Aug 6, 2019
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
13 changes: 9 additions & 4 deletions src/behavior-considered-undefined.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,14 @@
## Behavior considered undefined

Rust code, including within `unsafe` blocks and `unsafe` functions is incorrect
if it exhibits any of the behaviors in the following list. It is the
programmer's responsibility when writing `unsafe` code that it is not possible
to let `safe` code exhibit these behaviors.
Rust code is incorrect if it exhibits any of the behaviors in the following
list. This includes code within `unsafe` blocks and `unsafe` functions!
`unsafe` is not an excuse to cause undefined behavior.

It is the programmer's responsibility when writing `unsafe` code that it is not
possible to let `safe` code exhibit these behaviors. `unsafe` code that
satisfies this property for any `safe` client is called *sound*; if `unsafe`
code can be misused by `safe` code to exhibit undefined behavior, it is
*unsound*.

<div class="warning">

Expand Down