Weird definition of overlap

[Darksonn]

You define overlap as

Two values overlap when their memory locations overlap, or both values are elements of the same array.

So even if they don't overlap in memory location, but are part of the same array, they are still considered to overlap. However, you then define:

While a mutable reference is active, no other reference shall refer to a value that overlaps with the referent of the mutable reference.

But mutable references to arrays can usually be split into several references if they don't overlap in the conventional sense, but this contradicts the definition with arrays.

[jonas-schievink]

Yeah, these rules only apply when borrow checking manually created references, so we should clarify that. &mut a[0] and &mut a[1] conflict, but let [x,y,..] = a is fine (and so is an unsafe implementation like split_at_mut).

[Veykril]

We should re-phrase this in general. Phrasing this in terms of values seems a bit odd, we also don't specify that this is a borrowing restriction as outlined by Jonas.