Uh oh!
There was an error while loading. Please reload this page.
fix intra-link resolution spans in block comments - #56010
Conversation
QuietMisdreavus
left a comment
There was a problem hiding this comment.
This is brilliant, thank you so much! I was expecting the fix to be more complicated than this, but your PR is great!
QuietMisdreavus
commented
Nov 16, 2018
@bors r+ |
bors
commented
Nov 16, 2018
📌 Commit 9893407d87e81c2069ca06c416d316adbf562946 has been approved by |
bors
commented
Nov 19, 2018
☔ The latest upstream changes (presumably #56051) made this pull request unmergeable. Please resolve the merge conflicts. |
euclio
commented
Nov 19, 2018
@QuietMisdreavus Rebased. |
euclio
commented
Nov 26, 2018
Ping @QuietMisdreavus |
QuietMisdreavus
commented
Dec 3, 2018
@bors r+ |
bors
commented
Dec 3, 2018
📌 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. Fixesrust-lang#55964.
Uh oh!
There was an error while loading. Please reload this page.
euclio
commented
Dec 6, 2018
@QuietMisdreavus Added a test and made sure the compiler docs can be generated successfully. I think this solution is cleaner than the original, too! |
Uh oh!
There was an error while loading. Please reload this page.
euclio
commented
Dec 11, 2018
@QuietMisdreavus Ok, I think this is ready for bors to have another whack at it. |
QuietMisdreavus
commented
Dec 11, 2018
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+ |
bors
commented
Dec 11, 2018
📌 Commit 56413ec has been approved by |
bors
commented
Dec 11, 2018
⌛ Testing commit 56413ec with merge c4b3fc4bc2f0f9e068c9bf5b6bba2f0f240fd7d0... |
bors
commented
Dec 11, 2018
💔 Test failed - status-appveyor |
rust-highfive
commented
Dec 11, 2018
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 |
alexcrichton
commented
Dec 11, 2018
@bors: retry
|
bors
commented
Dec 12, 2018
⌛ Testing commit 56413ec with merge 6375777bb438d115b298003e93197110f881bba0... |
bors
commented
Dec 12, 2018
💔 Test failed - status-appveyor |
alexcrichton
commented
Dec 12, 2018
@bors: retry |
bors
commented
Dec 12, 2018
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
bors
commented
Dec 12, 2018
☀️ 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