RFC: overloaded slice notation

This RFC adds *overloaded slice notation*:

- `foo[]` for `foo.as_slice()`
- `foo[n..m]` for `foo.slice(n, m)`
- `foo[n..]` for `foo.slice_from(n)`
- `foo[..m]` for `foo.slice_to(m)`
- `mut` variants of all the above

via two new traits, `Slice` and `SliceMut`.

[Rendered](https://github.com/aturon/rfcs/blob/slice-notation/active/0000-slice-notation.md)
Yes, my hope is that we do *not* implement `Deref` on e.g. `Vec`, and instead add this slicing notation and implement the slice traits directly on `Vec` as you're suggesting.

But the ergonomics issue I'm most worried about is the need for `as_slice` in arguments.