compiler: Include span of too huge array with -Cdebuginfo=2
#146025
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.
We have a few ui tests to ensure we emit an error if we encounter too big arrays. Before this fix, compiling the tests with
-Cdebuginfo=2
would not include the spans of the instantiation sites, because the error is then emitted from a different code path that does not include the span.Propagate the span to the error also in the debuginfo case, so the tests passes regardless of debuginfo level.
r? @wesleywiser since this is a natural continuation of #145967 that you approved (thanks!).
cc #61117 since this takes is one step closer to increasing
rust.debuginfo-level-tests
to2
in the x86_64-gnu-debug CI job.Test failure output without the fix
Here is what the test failures look like if you run the tests without the fix. (Click to expand.)
As can be seen, the span info is missing with debuginfo=2 without the fix.