-
-
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
varargs[untyped]
doesn't work with 0 arguments, creating an extraneous nnkHiddenStdConv
varargs[untyped] node
#8706
Labels
Comments
This is especially annoying when we want to overload In Arraymancer this is blocking dereferencing my computation graph mratsim/Arraymancer#185, (and related macro to workaround does not work mratsim/Arraymancer#241 (comment)) |
LemonBoy
added a commit
to LemonBoy/Nim
that referenced
this issue
Aug 21, 2018
When an empty nkArgList `varargs[untyped]` is passed around it is now reused for efficiency sake and to prevent the introduction of a spurious element: before this commit we'd pass the caller a nkArgList[nkHiddenStdConv[nkBracket]] node instead of just an empty nkArgList. Fixes nim-lang#8706
LemonBoy
added a commit
to LemonBoy/Nim
that referenced
this issue
Aug 21, 2018
When an empty nkArgList `varargs[untyped]` is passed around it is now reused for efficiency sake and to prevent the introduction of a spurious element: before this commit we'd pass the caller a nkArgList[nkHiddenStdConv[nkBracket]] node instead of just an empty nkArgList. Fixes nim-lang#8706
Araq
pushed a commit
that referenced
this issue
Aug 31, 2018
When an empty nkArgList `varargs[untyped]` is passed around it is now reused for efficiency sake and to prevent the introduction of a spurious element: before this commit we'd pass the caller a nkArgList[nkHiddenStdConv[nkBracket]] node instead of just an empty nkArgList. Fixes #8706
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
see all mentions of BUG below:
see also workaround in case6 to create a macro
varargsToTuple
this is a serious bug as it affects generic code (eg I had to work around it for #8679)
The text was updated successfully, but these errors were encountered: