-
-
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
Regression in mapIt for enums #8566
Labels
Comments
LemonBoy
added a commit
to LemonBoy/Nim
that referenced
this issue
Aug 8, 2018
Don't try to be too smart and limit the use of `evalOnce` where strictly needed as not every value can be assigned with a `let`. Fixes nim-lang#8566
Thanks for spotting this edge case, it should be fixed now :) |
Araq
pushed a commit
that referenced
this issue
Aug 8, 2018
Don't try to be too smart and limit the use of `evalOnce` where strictly needed as not every value can be assigned with a `let`. Fixes #8566
timotheecour
pushed a commit
to timotheecour/Nim
that referenced
this issue
Aug 8, 2018
Don't try to be too smart and limit the use of `evalOnce` where strictly needed as not every value can be assigned with a `let`. Fixes nim-lang#8566
timotheecour
pushed a commit
to timotheecour/Nim
that referenced
this issue
Aug 8, 2018
Don't try to be too smart and limit the use of `evalOnce` where strictly needed as not every value can be assigned with a `let`. Fixes nim-lang#8566
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The commit ba5e2d6 causes a regression in the following code:
Raising
'typedesc' metatype is not valid here; typed '=' instead of ':'?
More specifically, this manifests within the
nim-chronicles
library here: https://github.com/status-im/nim-chronicles/blob/master/chronicles/options.nim#L106The text was updated successfully, but these errors were encountered: