-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Fix a couple broken links to the reference from error messages. #42624
Conversation
@@ -851,7 +851,7 @@ optional namespacing), a dereference, an indexing expression or a field | |||
reference. | |||
More details can be found here: | |||
https://doc.rust-lang.org/reference.html#lvalues-rvalues-and-temporaries | |||
https://doc.rust-lang.org/reference/expressions.html#lvalues-rvalues-and-temporaries |
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.
Longer than 80 characters. It fails tidy test.
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.
How do I fix this? Should I have tidy ignore this file?
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.
I believe the correct fix here is to change https://github.com/rust-lang/rust/blob/master/src/tools/tidy/src/style.rs#L55 to properly handle URLs in non-comment lines. I haven't looked into the exact fix, though. It might be non-trivial.
Once tidy issue fixed, r=me. |
ping @frewsxcv, just wanted to keep this on your radar! |
Still on my radar, just haven't had time to look into modifying the tidy checker. |
Pinging @frewsxcv for your weekly heartbeat 💓 ping |
I'm here. Haven't had time to look into this. I'm dealing with family issues right now and probably won't get to this anytime soon. Want me to close this and open a GitHub issue? |
Hi @frewsxcv, bit unfortunate this has turned into a bit of a yak shave! If 'soon' means a couple of weeks then closing this and opening an issue (referencing this PR as guidance for any future contributor) is probably better, otherwise keeping it around sounds fine. Up to you! |
Opened #43070 |
No description provided.