bump rustc-ap crates

[RalfJung]

For some reason I also had to do

cargo update -p crossbeam-utils --precise 0.6.5

as otherwise things wouldn't build. Even rustfmt master does not build for me. See crossbeam-rs/crossbeam#435.

[RalfJung]

This is the main point of the update: old memoffset is broken in many ways, and I am trying to remove it from the rustc dependency chain.

[RalfJung]

Well, CI is getting the same build failures as I did locally for crossbeam-channel. The odd part is that it seems to ignore the lockfile:

   Compiling crossbeam-utils v0.6.6

[calebcartwright]

Believe rust-lang/rust#65424 is probably still relevant on the crossbeam-utils front

[RalfJung]

Ah yes that would explain it.

I also learned rustc-ap updates need to be coordinated with Racer -- does that mean submitting a PR there as well, or more than that?

I updated these crates to version 610 instead of the latest (616) to keep the delta smaller. Not sure what the usual policy is here.

[calebcartwright]

I also learned rustc-ap updates need to be coordinated with Racer -- does that mean submitting a PR there as well, or more than that?

I think so, but @topecongiro would be able to answer definitively
/~https://github.com/rust-lang/rustfmt/blob/master/Processes.md#5-create-a-pr-to-rust-langrust-to-update-the-rustfmt-submodule

[topecongiro]

@RalfJung Thank you for the PR!

I also learned rustc-ap updates need to be coordinated with Racer -- does that mean submitting a PR there as well, or more than that?

Yes, updating the rustc-ap-* crates needs to be coordinated among repositories that are registered as submodules in the rustc repo.

I updated these crates to version 610 instead of the latest (616) to keep the delta smaller. Not sure what the usual policy is here.

Given that updating the rustc-ap-* crates are somewhat daunting, I prefer to update to the latest version if possible.

[RalfJung]

I bumped these in racer as well: racer-rust/racer#1078

Looks like a rustfmt release is needed to make RLS depend on the new version? What is the usual process here, do you just do that fairly regularly and we wait for the next cycle?

[topecongiro]

Looks like a rustfmt release is needed to make RLS depend on the new version?

Yes.

What is the usual process here, do you just do that fairly regularly and we wait for the next cycle?

We don't do this regularly but rather from the urgent need, e.g. supporting a new syntax or fixing the broken tool-state. I will make the next release within a day.

[topecongiro]

@RalfJung As a part of the next release, I will update rustc-ap-* crates to the latest version (617 or 618, depending on the timing).

[RalfJung]

There's no urgency to this, I am just trying to get memoffset 0.2 out of the rustc dependency graph.