At CppNorth a few weeks ago there was a lot of discussion about memory
safety in C++. I've been implementing a compiler with memory safety
and I thought maybe I should submit a series of proposals since I'm
already familiar with potential pitfalls, solutions and
implementation.

Attached is a proposal for safespan and nspan which requires certain
things to be known at compile time. I called the second type nspan
because it behaves differently from span. I'm not too concerned about
what these are eventually called