-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Stabilize 2018 edition #53999
Stabilize 2018 edition #53999
Conversation
Using this flag looks like this: | ||
|
||
```bash | ||
$ rustdoc src/lib.rs -Z unstable-options --edition 2018 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm... it is stable but still using unstable-options
?
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
cdb1847
to
b30ad60
Compare
b30ad60
to
6935a19
Compare
Okay, I believe this should work now, but still running tests locally. An interesting thing I noticed is that If this is expected we might want to alias some other feature to it since once we ship I'd rather not have users writing "preview". cc @Centril, @aturon Otherwise I believe this is ready for review |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
This looks good to me! r=me with green travis And yeah it's expected that transition lints don't fire unless the unstable feature is enabled. Once everything stabilizes though they'll fire by default. |
6935a19
to
8c3ac3c
Compare
Going to r+ this since I've run a good portion of tests locally... @bors r=alexcrichton |
📌 Commit 8c3ac3c has been approved by |
@bors p=1 |
⌛ Testing commit 8c3ac3c with merge affbf667000602372b2861aff5be6f8f0957fafa... |
This is probably going to fail just as #54036 due to crate vis modifier used as part 2018 without feature gate in clippy. |
Yes, that seems likely. I'll try to coordinate a fix. @bors r- |
@bors retry |
…o longer part of 2018 edition. Fixes build with rust-lang/rust#53999
rust-lang/rust-clippy#3150 will make clippy compatible with this PR. |
Ah, then we'll also have to update clippy_lints used in RLS and push a RLS update to rustc .... |
@matthiaskrgr |
Ah, excellent, I didn't notice that :D |
☀️ Test successful - status-travis |
You can see in the log that clippy build failed, yet bors didn't see this as a reason to mark the build as failed https://api.travis-ci.org/v3/job/425956240/log.txt |
I'll update this PR to include a clippy bump sometime today. |
In case you want it, I already have a rebased version with this PR + clippy bump in the pipeline but I didn't push yet because I wanted to wait until local testbuild is done. |
Yes, that would be great, thanks! |
Ok, it turned out that rls suffers from the same problem but we never got that far because clippy_lint dependency was already broken. I have to go AFK for most of the rest of the day in an hour or two, I allowed editing by maintainers on #54057 so once the fix is merged into rls, you can hopefully add that to the PR and it should be good to go... 😅 |
@Mark-Simulacrum @matthiaskrgr done, latest commit with the mentioned fix is rust-lang/rls@5b5cd9d cc #54057 |
…-clippy, r=alexcrichton Stabilize edition 2018; also updates Clippy and RLS Supersedes rust-lang#53999 Clippy build was failing there because crate_visibility_modifier feature was taken out of edition 2018 and clippy used it. The clippy update enables the corresponding feature explicitly. r? @Mark-Simulacrum
…Mark-Simulacrum Stabilize edition 2018; also updates Clippy, RLS and Cargo Supersedes #53999 , #53935 Clippy build was failing there because crate_visibility_modifier feature was taken out of edition 2018 and clippy used it. The clippy update enables the corresponding feature explicitly. r? @Mark-Simulacrum
r? @eddyb
cc @Centril @aturon