-
Notifications
You must be signed in to change notification settings - Fork 448
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
Allow local definition in comprehension syntax #90
Comments
Yeah this seems like a good idea. |
@sparkprime Is there still appetite for this? This is useful enough that I think (assuming our POC goes well) we could devote some attention to it. |
Heh I didn't see your comment until now. Yeah it would be nice, and it's probably no harder than tweaking the desugaring rule for comprehensions |
Any update on this? |
No update. The problem with doing language changes now is that they need to be done in both the Go and C++ branch. Anyone is welcome to do it though. |
* Fix comprehensions Only first and last forspec was used due to a parser bug.
For example I could replace the expression
{ [k]: processedField[k]
for field in std.objectFields(feature)
for processedField in [processFeature(field)]
for k in std.objectFields(processedField) }
with
which is a bit more clear syntactically.
The text was updated successfully, but these errors were encountered: