-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Allow bare CR in ////-style comment. #41827
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
@bors r+ rollup |
📌 Commit 0e8e45c has been approved by |
…ent, r=estebank Allow bare CR in ////-style comment. Fixes rust-lang#40624 in a way that bare CR is allowed in all non-doc comments.
@qnighy thanks for the bug fix! But I have a question. I think the more fundamental problem here is that the test for "is this a doc comment" is kind of "open-coded" here. That boolean that you modified might be better called "starts-with-triple-slash" or "is-maybe-doc-comment". If you look a bit later on in the file, you'll see some logic that invokes |
@nikomatsakis I've left it undone because |
@qnighy not that I know of... |
Fixes #40624 in a way that bare CR is allowed in all non-doc comments.