-
Notifications
You must be signed in to change notification settings - Fork 14.1k
Statically require links to an issue or the edition guide for all FCWs #149846
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
base: main
Are you sure you want to change the base?
Conversation
|
The rustc-dev-guide subtree was changed. If this PR only touches the dev guide consider submitting a PR directly to rust-lang/rustc-dev-guide otherwise thank you for updating the dev guide with your changes. |
| | | ||
| = warning: this is accepted in the current edition (Rust 2015) but is a hard error in Rust 2018! | ||
| = note: for more information, see issue #41686 <https://github.com/rust-lang/rust/issues/41686> | ||
| = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2018/trait-fn-parameters.html> |
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.
all 2018 edition FCWs had links to issues while there's a perfectly good edition guide page available
| LL | panic!("here's a brace: {"); | ||
| | ^ | ||
| | | ||
| = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/panic-macro-consistency.html> |
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.
example of an FCW without link
This comment has been minimized.
This comment has been minimized.
|
are there edition guide pages before an edition is done? like how does this work when the next edition is a WIP still |
|
This is fair. We currently aren't in that situation. The types model the current situation, but it's trivial to make the edition-related FCW an enum of either an issue or an edition guide page. I could do this now, or whenever that's relevant in the future. |
|
Probably makes sense to do so now so that any future efforts for editions don't get blocked on misc-infra work |
8df328b to
897e78f
Compare
|
I feel like since we have a concept of a "future" edition, it also makes sense to have pages in the edition guide for the changes in that "future" edition. |
This comment has been minimized.
This comment has been minimized.
897e78f to
bfc890c
Compare
bfc890c to
8548b27
Compare
|
@rustbot review |
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.
r=me with nit and ci
| .emit(); | ||
| ``` | ||
|
|
||
| Or better: a structured like this: |
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.
nit: I'm not sure what this sentence means. A structured what?..
8548b27 to
183048c
Compare
|
@bors r=wafflelapkin |
|
@bors rollup |
…=wafflelapkin Statically require links to an issue or the edition guide for all FCWs r? `@wafflelapkin`
Rollup of 7 pull requests Successful merges: - #148052 (Stabilize `const_mul_add`) - #149386 (Display funding link in the github overview) - #149489 (Experimentally add *heterogeneous* `try` blocks) - #149764 (Make `--print=backend-has-zstd` work by default on any backend) - #149838 (Build auxiliary in pretty tests) - #149839 (Use `PointeeSized` bound for `TrivialClone` impls) - #149846 (Statically require links to an issue or the edition guide for all FCWs) r? `@ghost` `@rustbot` modify labels: rollup
r? @WaffleLapkin