Tobias Bucher

Sounds great!

This is a backward-compatiblity hazard. E.g.: It seems that `libcore` is getting default features, relatively harmless ones, they change some formatting. Some crate today might opt out of default features...

Note that I don't talk about hard-disabling dependency feature, but rather the equivalent of today's `default-features = false` and then a list of all the other features in the `features...

@Stebalien Waiting for rust-lang/rfcs#1615.

I'll rebase the patch or the partial patch if this gets accepted. This won't be the problem.

I don't see that this brings much benefit. The parts you moved outside of the `unsafe` blocks are part of the code that upholds the safety.

> Storing the length as [`NonMaxU32`](https://docs.rs/nonmax/latest/nonmax/struct.NonMaxU32.html) would allow compiler to optimize `Option` size by storing `None` as impossible length value (`u32::MAX`). This type looks bad for use with `ArrayVec`, it...

> It is very cheap operation, doesn't it? It's also a useless one. It'd better if Rust could use 0xffff_ffff as a niche. Alternatively, adding 1 to the length might...

I'm not sure that this needs a breaking change.

I'd like to move `linear_map`. What do I have to do?