Improve coverage spans for chained function calls #84529
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #84180
For chained function calls separated by the
?
try operator, thefunction call following the try operator produced a MIR
Call
span thatmatched the span of the first call. The
?
try operator started a newspan, so the second call got no span.
It turns out the MIR
Call
terminator has afunc
Operand
for the
Constant
representing the function name, and the functionname's Span can be used to reset the starting position of the span.
r? @tmandry
cc: @wesleywiser