Improve error messages for type application mismatches #1668
+634
−243
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.
CHANGELOG.md
for any new functionalityREADME.md
updated for any listed functionalityThis PR improves error messages for type application mismatches, specifically addressing the confusing errors users receive when using a List where a Set is expected (like in the map function).
Changes
TypeApplicationErrorDetails
interface to store detailed error informationbuildTypeApplicationMismatchLeaf
function to create more user-friendly error messageserrorTreeToString
to display clearer error messages with expected/actual typesunify
inconstraintSolver.ts
to provide operator information when detecting mismatchesFix Error messages for type application mismatch are not clear #1361