est31

I've just recreated the table on the latest rustc, and it is like before (I've [added some extra lines](https://github.com/rust-lang/cargo/pull/8437#issuecomment-653842297)): | cargo command | lib.rs | main.rs | lib.rs cfg test...

cc @mitchmindtree on this, as they authored most of the code. In general, the license files are already present in the git repo, they are just not in the particular...

#188 is merged now, now only a release is missing.

Through trial and error I've determined that current master needs at least Rust 1.32.0. Rust 1.31.0 doesn't work because there, macro_literal_matcher isn't stable yet. This is incurred by code in...

That's interesting, it seems that `BufferAny` has a parameter to allow you setting a custom `elements_size`.

Negative indices in C mean something completely different and are super scary ([but are defined behaviour](https://stackoverflow.com/a/3473684)!!). Imitating the python behaviour will be surprising to anyone with a C/C++ background and...

> but first let's figure out if we want "indexing starting from the end" or not. A question that every proposal to change the language has to answer: why should...

> Therefore it has to be in libcore, or no dice. @Centril good point! > For the wrapping_index example, it makes sense that wrapping_index(i) is equivalent to [i % len]...

> Right now, thinking again, it still makes sense to support signed indices for the sake of ranges. For example, 2..from_end(1) simply won't work. Right now, `Range` is a struct...

Also, if you went with the signed indices proposal, you'd have to change how the compiler is doing inference when it sees an indexing operation in order to make stuff...