Fix coverage ICE because fn_sig can have a span that crosses file bou… #84532
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: #83792
MIR
InstrumentCoverage
assumed theFnSig
span was contained within asingle file, but this is not always the case. Some macro constructions
can result in a span that starts in one
SourceFile
and ends in adifferent one.
The
FnSig
span is included in coverage results as long as that span isin the same
SourceFile
and the same macro context, but by assuming theFnSig
span'shi()
andlo()
were in the same file, I took this forgranted, and checked only that the
FnSig
hi()
was in the sameSourceFile
as thebody_span
.I actually drop the
hi()
though, and extend theFnSig
span to thebody_span.lo()
, so I really should have simply checked that theFnSig
span'slo()
was in theSourceFile
of thebody_span
.r? @tmandry
cc: @wesleywiser