Type checker: use inner expr range in upcast constraints errors #18850
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.
Makes type checker use inner expression range for upcast errors. It makes it more in-line with other type constraint errors and makes it easier to distinguish cases where upcast expressions themselves do not satisfy the constraints.
Before this change the same range was used for errors about
bnot being compatible withT2and forT2not being compatible withT1:With this change the first error covers
brange only.