[GR-60554] Improve causalilty reporting for unresolved elements. #10320
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.
SharedBytecodeParser#maybeEagerlyResolve(int, int)swallows certain exceptions in the expectation that the exception being swallowed will be re-thrown anyway in a subsequent step. However, this is not always the case. To mitigate loss of exception causality in this scenario, the swallowed exception should be saved so that it can be included when reporting an unresolved element.The result of this PR is best shown with this diff: