We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fn main() { var x: int32 = "a"; // Error: Incompatible types int32 and str var y: int32 = "b"; // not reported }
Reporting more than a single type error per compiler invocation (see this godbolt/compiler-explorer page) is good because it saves time.
The text was updated successfully, but these errors were encountered:
Yes, the compiler (not only the type checker) always stops on the first error and does not try to recover.
Sorry, something went wrong.
I'm personally like it this way. A lot of compilers that report multiple errors can report errors that only exist because of other errors.
No branches or pull requests
Reporting more than a single type error per compiler invocation (see this godbolt/compiler-explorer page) is good because it saves time.
The text was updated successfully, but these errors were encountered: