Uh oh!
There was an error while loading. Please reload this page.
Don't recommend extern crate syntax - #63289
Conversation
rust-highfive
commented
Aug 5, 2019
r? @zackmdavis (rust_highfive has picked a reviewer for you, use r? to override) |
rust-highfive
commented
Aug 5, 2019
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 |
tesuji
commented
Aug 5, 2019
But what about Rust 2015 edition? |
The new message is valid for both 2015 and 2018 editions. It's not as helpful for 2015, but also it's not misleading for the 2018 edition. Given that 2015 exists only for backwards compatibility, I don't think it's worth to maintain two different messages for two editions. And if there's one message, it should favor the current edition. |
Centril
commented
Aug 5, 2019
zackmdavis
commented
Aug 8, 2019
@bors r+ rollup |
bors
commented
Aug 8, 2019
📌 Commit 3bfb4c3 has been approved by |
Don't recommend `extern crate` syntax `extern crate` syntax is not a good recommendation any more, so I've changed it to just print a suggested crate name.
Rollup of 6 pull requests Successful merges: - #63162 (Miri tests: use xargo to build separate libstd) - #63289 (Don't recommend `extern crate` syntax) - #63373 (gitignore: add comment explaining policy) - #63374 (move of packed fields might or might not occur when they actually are sufficiently aligned) - #63381 (reduce visibility) - #63387 (Test interaction between `async { ... }` and `?`, `return`, and `break`) Failed merges: r? @ghost
extern cratesyntax is not a good recommendation any more, so I've changed it to just print a suggested crate name.