-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
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
Can we improve error message for wrong proc result type? #16150
Comments
columns start at 0 but the point is indeed that the column isn't sufficient to disambiguate, you'll get the same column if you write => fixing this in #16152 |
Nope, the issue here is that the error message is pointing to the call braces, not the sym of the callee. |
* fix nim-lang#16150 improve type mismatch errors * allow -d:nimLegacyTypeMismatch * address comment
* fix nim-lang#16150 improve type mismatch errors * allow -d:nimLegacyTypeMismatch * address comment
In a similar but much more complicated case I got from the error message the impression that the argument of the proc has wrong type. Took me a few minutes to recognize that problem is the proc result.
Error pos column 6 is the start of the proc argument, and when argument and return types are both exotic types it is confusing.
The text was updated successfully, but these errors were encountered: