-
-
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
Cannot hand multiple procs to macro using varargs[typed]
#13913
Comments
ynfle
added a commit
to ynfle/Nim-1
that referenced
this issue
Jan 31, 2022
There was a bug that params wouldn't be matched if the param was overloaded and the candidate type was varargs. This checks the base type of the `varargs` and then will to an overloaded symbol if in a macros or template. Closes nim-lang#19446 & nim-lang#13913
ynfle
added a commit
to ynfle/Nim-1
that referenced
this issue
Jan 31, 2022
There was a bug that params wouldn't be matched if the param was overloaded and the candidate type was varargs. This checks the base type of the `varargs` and then will to an overloaded symbol if in a macros or template. Fixes nim-lang#19446 Fixes nim-lang#13913
ynfle
added a commit
to ynfle/Nim-1
that referenced
this issue
Jan 31, 2022
There was a bug that params wouldn't be matched if the param was overloaded and the candidate type was varargs. This checks the base type of the `varargs` and then will to an overloaded symbol if in a macros or template. Fixes nim-lang#19446 & nim-lang#13913
ynfle
added a commit
to ynfle/Nim-1
that referenced
this issue
Jan 31, 2022
There was a bug that params wouldn't be matched if the param was overloaded and the candidate type was varargs. This checks the base type of the `varargs` and then will to an overloaded symbol if in a macros or template. Fixes nim-lang#19446 & nim-lang#13913
ynfle
added a commit
to ynfle/Nim-1
that referenced
this issue
Jan 31, 2022
There was a bug that params wouldn't be matched if the param was overloaded and the candidate type was varargs. This checks the base type of the `varargs` and then will to an overloaded symbol if in a macros or template. Fixes nim-lang#19446 & nim-lang#13913
ynfle
added a commit
to ynfle/Nim-1
that referenced
this issue
Feb 3, 2022
There was a bug that params wouldn't be matched if the param was overloaded and the candidate type was varargs. This checks the base type of the `varargs` and then will to an overloaded symbol if in a macros or template. Fixes nim-lang#19446 & nim-lang#13913
ynfle
added a commit
to ynfle/Nim-1
that referenced
this issue
Apr 14, 2022
There was a bug that params wouldn't be matched if the param was overloaded and the candidate type was varargs. This checks the base type of the `varargs` and then will to an overloaded symbol if in a macros or template. Fixes nim-lang#19446 & nim-lang#13913
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was writing some code where I wanted to get all possible overloads for different procedures in an untyped macro. The experimental
dynamicBindSym
actually worked for that, but @Araq advised against using it.So I tried to hack my way around it by having a helper macro, which receives the results of
bindSym
calls as arguments. After being confused by "undeclared identifier errors" on another actually untyped argument (which turned out to be this really annoying bug: #12019), I figured out the problem is rather simple.Example
Current Output
Expected Output
Each
t
in the for loop should be annnkClosedSymChoice
as in this example with a single proc and no varargs:Possible Solution
I'm not even sure if this is allowed and not actually a bug. But I don't know why it wouldn't. Every argument is just a
NimNode
, no?Additional Information
I was on:
and just updated to current devel and the problem persists:
The text was updated successfully, but these errors were encountered: