Consider a replace_nonoverlapping() that is unsafe but uses __restrict to say the inputs don't overlap

[danakj]

This could possibly be used for example in IteratorLoop, would it allow the compiler to optimize better in cases where we are replacing a value with a value (not a reference) that we thus know can't alias?