Better reporting #16
Merged
Better reporting #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 improves upon #15 by improving the reporting.
The formatting of the text that is emitted as a warning or error has been improved. It is now more legible and includes a short stack trace for warnings as well. This makes it easier to locate problems.
It is now possible to set the default value globally for type check strictness and reporting, whilst still allowing override with implicit variables.
Finally, this PR includes a small fix for stream duplicators. Now the duplicator will use the same datatype as in the template, avoiding a mismatched type exception/warning.