-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
cargo fix prepare-for 2018 errors after due to 'async' identifier #5783
Comments
Just hit this right now with EDIT: Except raw identifiers are still an unstable feature, should they be ungated in 2018 even though they're still unstable since they are essential for transitioning in some cases? |
Thanks for the report @seanmonstar and @Nemo157! It looks like this may be a bug in the lint and/or compiler. To confirm, if you place If so, I'll fix this in rustc. If not, there's more digging to do! |
@alexcrichton |
Ok great, thanks for checking @Nemo157! |
* Enable the `raw_identifiers` feature automatically in the 2018 preview * Only emit lint warnings if the `raw_identifiers` feature is activated cc rust-lang/cargo#5783
Tweak the raw_identifiers lints in 2018 * Enable the `raw_identifiers` feature automatically in the 2018 preview * Only emit lint warnings if the `raw_identifiers` feature is activated cc rust-lang/cargo#5783
Ok the fixes are now in nightly and with @Nemo157's confirmation it worked I'm gonna close, we can always reopen if this comes up again though! |
I tried out
cargo fix --prepare-for 2018
on hyper, and after it ran, it showed an error and claimed it was a bug in cargo or rustc, and to report it here. There is an identifier currently namedasync
in a file, here: https://github.com/hyperium/hyper/blob/069a32b1acc5ece35643c26cf5d9972dace5481c/src/body/body.rs#L268In this specific case, it would have been fine to just renamed that binding to
async_
, or perhapsr#async
. I'm not sure if trying to do that automatically would accidentally nameasync
blocks or functions wrongly, though.The text was updated successfully, but these errors were encountered: