Release 0.10.7 breaks semver compatibility

[RReverser]

Copying comment from #66:

@dtolnay Looks like you released it in 0.10.7 because @SimonSapin bumped version as part of his commit 07c7341 and thus broke semver - our build started failing with Use of undeclared type or module `BlockCheckMode` when Cargo started auto-pulling 0.10.7 instead of 0.10.6 :(

Maybe it's worth to unpublish release from Cargo? (I'm pretty sure we're not the only one whose build was broken)

[SimonSapin]

Ah, this is my mistake. I branched my PR #83 from 881a5ef "Merge tag 0.10.6 into master", but I should have used 66a31d6 (tag: 0.10.6) "Release 0.10.6" instead. The former probably includes breaking changes from another branch.

I think 0.10.7 should be yanked from crates.io. @dtolnay, I’d appreciate if you could also make 0.10.8 with the unicode-xid upgrade from the correct base. I can provide a PR if you’d like, but since it’s a small change it might be easier to do it yourself?

[SimonSapin]

@RReverser In the meantime, I think cargo update -p syn --precise 0.10.6 should fix your build.

[RReverser]

@SimonSapin Not on Travis (unless we commit Cargo.lock too which is likely not what we want to do at the moment; alternatively could add this command to .travis.yml but then it seems better and more reliable to just yank this version).

[SimonSapin]

Yes, this version should be yanked. This was just an attempt to unblock you until dtolnay can get around to doing it.

[RReverser]

@SimonSapin Yeah, appreciate that.

[dtolnay]

I yanked 0.10.7 and published 0.10.8 for @SimonSapin based on the correct commit. Really sorry about the break here.

[RReverser]

@dtolnay All good, thanks for the fast turnaround!