Detailed error messages #7
Open
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.
This PR builds on the changes in #6, so it'd be best to merge that before reviewing, or start reviewing after the duplicated commits.
Major changes:
.toString()method to all Types which returns a typescript-like representation of the type instance. This allows us to print types in error messages.Errtype that tracks path, error causes, and error types.Errmessages can be lazy() => stringinstead ofstring, avoiding expensive string building unless an exception is being raised, which makesType#sliceResulteven expensive.Errorclass thrown for assertions,StructuralError, which collects the root causes of a type error, enumerating the keys that did not match an expected type.Example of exception output:
That exception has these root causes: