clippy
This commit is contained in:
parent
a1bc030b70
commit
abbe244a81
@ -17,6 +17,7 @@ enum PermissionPriv {
|
||||
/// is relevant
|
||||
/// - `conflicted` is set on foreign reads,
|
||||
/// - `conflicted` must not be set on child writes (there is UB otherwise).
|
||||
///
|
||||
/// This is so that the behavior of `Reserved` adheres to the rules of `noalias`:
|
||||
/// - foreign-read then child-write is UB due to `conflicted`,
|
||||
/// - child-write then foreign-read is UB since child-write will activate and then
|
||||
|
@ -230,6 +230,7 @@ mod spurious_read {
|
||||
/// - any access to the same location
|
||||
/// - end of one of them being protected
|
||||
/// - a retag that would change their relative position
|
||||
///
|
||||
/// The type `TestEvent` models these kinds of events.
|
||||
///
|
||||
/// In order to prevent `x` or `y` from losing their protector,
|
||||
|
@ -1106,7 +1106,7 @@ trait EvalContextPrivExt<'mir, 'tcx: 'mir>: MiriInterpCxExt<'mir, 'tcx> {
|
||||
/// Temporarily allow data-races to occur. This should only be used in
|
||||
/// one of these cases:
|
||||
/// - One of the appropriate `validate_atomic` functions will be called to
|
||||
/// to treat a memory access as atomic.
|
||||
/// treat a memory access as atomic.
|
||||
/// - The memory being accessed should be treated as internal state, that
|
||||
/// cannot be accessed by the interpreted program.
|
||||
/// - Execution of the interpreted program execution has halted.
|
||||
|
Loading…
x
Reference in New Issue
Block a user