-
-
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
Experimental .
operator confuses the dot call syntax notation
#7777
Labels
Comments
This was referenced Feb 9, 2021
metagn
added a commit
to metagn/Nim
that referenced
this issue
Nov 26, 2022
Araq
pushed a commit
that referenced
this issue
Nov 28, 2022
survivorm
pushed a commit
to survivorm/Nim
that referenced
this issue
Feb 28, 2023
* better error messages for dot operators [backport] fixes nim-lang#13063 * also fixes nim-lang#7777 * fix nim-lang#6981 and nim-lang#9831 too * fix * minor improvement * sus test fixes * make test multiplatform lol * fix nimsuggest test, extra improvements
capocasa
pushed a commit
to capocasa/Nim
that referenced
this issue
Mar 31, 2023
* better error messages for dot operators [backport] fixes nim-lang#13063 * also fixes nim-lang#7777 * fix nim-lang#6981 and nim-lang#9831 too * fix * minor improvement * sus test fixes * make test multiplatform lol * fix nimsuggest test, extra improvements
bung87
pushed a commit
to bung87/Nim
that referenced
this issue
Jul 29, 2023
* better error messages for dot operators [backport] fixes nim-lang#13063 * also fixes nim-lang#7777 * fix nim-lang#6981 and nim-lang#9831 too * fix * minor improvement * sus test fixes * make test multiplatform lol * fix nimsuggest test, extra improvements
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been struggling with a hard to track down bug in my protobuf library for quite a while now. I couldn't for the life of me figure out what the error message I got meant. The problem was a simple missing export marker on a template, but the error pointed to something completely different. The below example shows what I'm talking about:
Error 1 (this is what we would normally see):
Error: undeclared identifier: 'getField'
Error 2 (this is what confused me):
Error: undeclared identifier: 'private_field'
If we remove the comments on the
getField
proc both examples workThe text was updated successfully, but these errors were encountered: