-
-
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
Unclear error message when assigning ambiguous proc to variable #6359
Comments
This happens for any routines with the same name, not necessarily with the same signature. A possible error message would be:
If one of the routines has empty arguments, it would also say |
It's not a call ... you're trying to get a pointer to the proc. |
…ang#20932) * better procvar ambiguity errors, clean up after nim-lang#20457 fixes nim-lang#6359, fixes nim-lang#13849 * only trigger on closedsymchoice again * new approach * add manual entry for ambiguous enums too * add indent [skip ci] * move to proc
…ang#20932) * better procvar ambiguity errors, clean up after nim-lang#20457 fixes nim-lang#6359, fixes nim-lang#13849 * only trigger on closedsymchoice again * new approach * add manual entry for ambiguous enums too * add indent [skip ci] * move to proc
…ang#20932) * better procvar ambiguity errors, clean up after nim-lang#20457 fixes nim-lang#6359, fixes nim-lang#13849 * only trigger on closedsymchoice again * new approach * add manual entry for ambiguous enums too * add indent [skip ci] * move to proc
Test
Result:
My original case wasn't as obvious as this example. I would expect a message along the lines of
Error: ambiguous call; both ...
The text was updated successfully, but these errors were encountered: