-
Notifications
You must be signed in to change notification settings - Fork 193
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
Automagically wrap AbstractOperation
and Reduction
in Field
inside OutputWriters
?
#2242
Comments
I think this is certainly more intuitive for users!
Pardon if this question is naive but why is it important that users to exposed to the |
Because that way they are prepared to do sophisticated post-processing! But I think you're right, maybe it's not a real "downside". |
Done |
This came up on #2235.
The idea is to support syntax like
rather than requiring things to be wrapped in
Field
to work.This wasn't easy to support previously, before we consolidate all the
Field
implementations (we hadComputedField
,Field
,AveragedField
...). But now we can support it and it would reduce boilerplate (eg everything isField(this)
,Field(that)
by quite a bit for the majority of use cases.I think the downside is that users aren't immediately exposed to
Field
infrastructure. A good "Fields tutorial" in the docs might help with that though.The text was updated successfully, but these errors were encountered: