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
Different symbol resolution in generic types depending on f(x)
vs f x
call syntax
#23406
Comments
Culprit is probably: Line 2028 in c2c0077
Should be |
metagn
added a commit
to metagn/Nim
that referenced
this issue
Mar 15, 2024
This was referenced Mar 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When a generic type is defined as a routine invocation, it—surprisingly—matters whether the call has parentheses or not.
Nim Version
Nim Compiler Version 2.0.2 [Linux: amd64]
Compiled at 2023-12-15
Copyright (c) 2006-2023 by Andreas Rumpf
git hash: c4c44d1
active boot switches: -d:release
Current Output
Expected Output
No response
Possible Solution
No response
Additional Information
It seems to be irrelevant whether
helper
hasuntyped
,typed
, ortype
parameter / return value. As I see, the only thing that matters is whether the command-call syntax is used for the top-level call.This bug has been existing since at least 0.19—that’s the oldest Nim I have on my system to check.
The text was updated successfully, but these errors were encountered: