-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Updating lints page to reflect recent changes #127504
Updating lints page to reflect recent changes #127504
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ehuss (or someone else) some time within the next two weeks. Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (
|
This comment has been minimized.
This comment has been minimized.
src/doc/rustc/src/lints/index.md
Outdated
|
||
$ rustc main.rs | ||
|
||
error[E0793]: reference to packed field is unaligned |
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.
that's not actually a future incompat lint now, it's just an error, you need a different example. search for @future_incompat
in the compiler source to find examples
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.
Thanks @Nilstrieb , I learned a lot hunting these down.
I'm not entirely sure it is a good idea to try to change this to a new lint example. The set of future-incompatible lints is constantly changing, and in a few months or years this would likely just be back where it started. It's not clear to me what kind of concern the original issue poster was having, or why they wanted to recreate the output. For me, the existing text seems pretty clear that this is just an illustrative example of what it might look like. Can you say more about why it is important to have an example that is triggered in the current compiler? |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@ehuss I submitted a change before reading your comment. That makes total sense, it looks fine to me as is. I have just tested it myself and can see that unaligned references is already a hard error anyway:
So I will leave this as is and close out this PR without merge. |
Closes #102743