-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crates using placement syntax behind a cfg broken #50832
Comments
It is already fixed in |
Oh, that's annoying. We should patch rayon-hash. |
This is not the first time this is happening, removal of |
Discussed in the @rust-lang/compiler meeting. I think we reached this consensus:
|
Some discussion of the final at or around here in the IRC logs https://botbot.me/mozilla/rustc/2018-05-17/?msg=100165163&page=3 |
triage: P-high |
Would anyone have time to whip up a change to the parser? cc @rust-lang/compiler @aidanhs |
For reference, the PR that reverted the syntax was #48333 |
I am working on rayon-hash. The quick hack would be to just nuke the placement stuff, but I'm trying to do a proper update to catch up to But frankly, I don't know of anyone really using rayon-hash anyway. |
Fixed in rayon-hash 0.3.0. |
I'll handle this. |
Restored in #51052 |
We could try calling more attention to lib authors about this through the API guidelines. |
restore emplacement syntax (obsolete) Fix #50832 r? @petrochenkov
The two regressions where about
Would it be ok to create a PR removing the |
Detect `for _ in in bar {}` typo Fix rust-lang#36611, rust-lang#52964, without modifying the parsing of emplacement `in` to avoid further problems like rust-lang#50832.
Some crates were using
<-
behind a feature flag, so they worked on stable even if the placement syntax was nightly-only. After removing it though they fail to compile even on stable with a syntax error, because<-
is not recognized anymore.The text was updated successfully, but these errors were encountered: