WIP #4721 try improving errors #4970
Closed
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.
When a type argument violates its bounds, we give the same errors whether the argument is specified by the user or inferred by the compiler. This PR is an (incomplete) attempt to detect and fix that. However, I failed to distinguish reliably inferred and synthesized type arguments, even following #4946 (comment)
This PR builds on #4946 to try improving the resulting error output. Sadly, the position of inferred arguments fails both
isSynthetic
andisZeroExtent
(arg.pos [53..54], false
).