@run:0

`Box<T, G>` is a `ScalarPair` where the 2nd component is the allocator.

`Box<T, G>` is an `Aggregate`.

Gather all references from a mutable iterator and make sure Miri notices if using them is dangerous.

Gather all references from a mutable iterator and make sure Miri notices if using them is dangerous.

Gather all references from a mutable iterator and make sure Miri notices if using them is dangerous.

Ensures that we get the same behavior across all targets.

Regression tests for slice methods in the Rust core library where raw pointers are obtained from mutable references.

Stacked Borrows would not have liked this one because the `as_mut_ptr` reborrow invalidates the earlier pointer obtained from `as_ptr`, but Tree Borro

Ensure that time passes even if we don't sleep (but just work).

This also internally uses offset_from.

@run:1 miri: @compile-flags: -Zmiri-tree-borrows This test tests that TB's protector end semantics correctly ensure that protected activated writes ca

This strips provenance

Traverses all children of `start_idx` including `start_idx` itself. Uses `f_continue` to filter out subtrees and then processes each node with `f_prop

Like `traverse_this_parents_children_other`, but skips the children of `start_idx`. Returns the index of the root of the accessed tree.

This function checks that there is no issue with having two mutable references from the same allocation both under a protector. This is safe code, it

This one really shouldn't be accepted, but since we treat 2phase as raw, we do accept it. Tree Borrows rejects it.

Make sure that we can create two raw pointers from a mutable reference and use them both.

Currently, if we do not know for a tag if an access is local or foreign, then we do not do any state transitions on that tag. However, to implement pr