leo error reporting after build #28327
Open
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.
Motivation
When developing complex Leo programs, it's not uncommon to encounter multiple compilation errors. This feature, inspired by Rust's error reporting system, provides developers with a clear overview of the number of errors and warnings in their code. Having a precise count of issues serves as a motivational tool, allowing developers to track their progress as they address and resolve bugs. The satisfaction of seeing the error count decrease provides positive reinforcement throughout the debugging process, ultimately enhancing the overall development experience and potentially improving code quality.
Test Plan
Run a leo program that generates errors and warnings.
Here is an example of what it looks like:
