Josh Stone

Maybe there's a way to get that across in the rust-analyzer installation docs? Something roughly like, "rustup provides a component for rust-analyzer that's contemporary with each stable/beta/nightly toolchain, but this...

> New users shouldn't know that "you need to install rustup to use rust-analyzer", new-users should just configure their editor. My take is more that new users should get their...

FYI, the `rust-analyzer` component is present and working with the new `1.64.0-beta.1` toolchain!

`rls` and `rust-analyzer` are both available components. If you update an existing installation, you'll only get updates to your previously installed components. Try `rustup component add rust-analyzer`. If you start...

FWIW, I was playing with an implementation of this a while ago. It's rather simple to handle this entirely in the parser, although I didn't add stability-gating or anything like...

cc @ignatenkobrain for Fedora too.

Did you consider using `dropping` instead of `skip`? That changes the laziness, but you did use `nth` in `IteratorIndex for usize`, which has the same immediate effect. edit: I guess...

Another consideration -- slice `get(range)` returns new slices, but `get(usize)` just returns the element, whereas you have `IteratorIndex` returning new iterators in all cases. But if iterator `get(usize)` were to...

Tying back to rayon, there's also the `ndarray-parallel` crate... (and isn't `ndarray` itself supposed to be getting rayon support?)

You make a reasonable point. I'm pretty sure that line exists from before `shift_remove` existed, and probably while the crate was still called `ordermap`. There is also still a caveat...