-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Field name causes Error: ambiguous identifier
for no relevant Reason
#136
Comments
I assume Module C is the module that calls NimYAML functionality ( That being said, the const in Module A you show does not seem to be the issue at all. The error says
The second My advice would be to call NimYAML somewhere where |
Fixed it like this. import std/logging except debug Thank you very much! 🙂 |
https://github.com/theAkito/zoominvitr/actions/runs/5957435803/job/16160211615#step:7:638
Module A
Module B
Module A has no relationship whatsoever to Module B. They do not import each other, nothing. The only way, they are in some way connected is that Module C is importing both at the same time.
Module B also imports
yaml
, while Module A does not.So, how does
serialization.nim
know and, most importantly, care about a constant from a foreign module? How does this even collide?Do the fields need to be unique across the project?
This is the related code snippet from
serialization.nim
.When re-defining
ConfigSettings.debug
asConfigSettings.sDebug
, compilation succeeds, because the names are different.The text was updated successfully, but these errors were encountered: