-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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 intra-link resolution spans in block comments #56010
Conversation
cefcfce
to
9893407
Compare
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.
This is brilliant, thank you so much! I was expecting the fix to be more complicated than this, but your PR is great!
@bors r+ |
📌 Commit 9893407d87e81c2069ca06c416d316adbf562946 has been approved by |
☔ The latest upstream changes (presumably #56051) made this pull request unmergeable. Please resolve the merge conflicts. |
9893407
to
ea5843c
Compare
@QuietMisdreavus Rebased. |
Ping @QuietMisdreavus |
@bors r+ |
📌 Commit ea5843c has been approved by |
…reavus fix intra-link resolution spans in block comments This commit improves the calculation of code spans for intra-doc resolution failures. All sugared doc comments should now have the correct spans, including those where the comment is longer than the docs. It also fixes an issue where the spans were calculated incorrectly for certain unsugared doc comments. The diagnostic will now always use the span of the attributes, as originally intended. Fixes rust-lang#55964.
ea5843c
to
5ba7a0e
Compare
@QuietMisdreavus Added a test and made sure the compiler docs can be generated successfully. I think this solution is cleaner than the original, too! |
@QuietMisdreavus Ok, I think this is ready for bors to have another whack at it. |
Curious about what caused that error in the first place, but if we can get around it, that's probably best for now. The new code looks good, so here goes... @bors r+ |
📌 Commit 56413ec has been approved by |
⌛ Testing commit 56413ec with merge c4b3fc4bc2f0f9e068c9bf5b6bba2f0f240fd7d0... |
💔 Test failed - status-appveyor |
Your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. 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 |
@bors: retry
|
⌛ Testing commit 56413ec with merge 6375777bb438d115b298003e93197110f881bba0... |
💔 Test failed - status-appveyor |
@bors: retry |
fix intra-link resolution spans in block comments This commit improves the calculation of code spans for intra-doc resolution failures. All sugared doc comments should now have the correct spans, including those where the comment is longer than the docs. It also fixes an issue where the spans were calculated incorrectly for certain unsugared doc comments. The diagnostic will now always use the span of the attributes, as originally intended. Fixes #55964. r? @QuietMisdreavus
☀️ Test successful - status-appveyor, status-travis |
This commit improves the calculation of code spans for intra-doc
resolution failures. All sugared doc comments should now have the
correct spans, including those where the comment is longer than the
docs.
It also fixes an issue where the spans were calculated incorrectly for
certain unsugared doc comments. The diagnostic will now always use the
span of the attributes, as originally intended.
Fixes #55964.
r? @QuietMisdreavus