You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
import module2
import module3
echo test # this produces the error
The error message shows the module name where the test is originally defined (module1 and module3), but it show where it is imported (module2 and module3).
Nim Version
Nim Compiler Version 2.0.2 [Linux: amd64]
Current Output
Error: ambiguous identifier: 'test' -- use one of the following:
module1.test: string
module3.test: string
Expected Output
Error: ambiguous identifier: 'test' -- use one of the following:
module2.test: string
module3.test: string
Possible Solution
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
I think #23123 broke this more. This is the result after commit b280100:
Error: type mismatch
Expression: echo test
[1] test: string | string
Expected one of (first mismatch at [position]):
[1] proc echo(x: varargs[typed, `$`])
I knew there was a different error message now given I disabled tpure_enums_conflict in #23123 but I didn't consider it completely obscures which symbols are ambiguous, I have an idea of what to do now but it's a bit verbose
metagn
added a commit
to metagn/Nim
that referenced
this issue
Sep 7, 2024
Description
Minimal example:
File module1.nim:
File module2.nim:
File module3.nim:
File main.nim:
The error message shows the module name where the
test
is originally defined (module1
andmodule3
), but it show where it is imported (module2
andmodule3
).Nim Version
Nim Compiler Version 2.0.2 [Linux: amd64]
Current Output
Expected Output
Possible Solution
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: