-
-
Notifications
You must be signed in to change notification settings - Fork 415
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
RFC: Sugar for Method Chaining #1409
Comments
I have an almost ready implementation for this so I'll assign myself. |
This change provides a way to chain calls on an object without depending on the method's API. Closes ponylang#1409.
This change provides a way to chain calls on an object without depending on the method's API. Closes ponylang#1409.
This change provides a way to chain calls on an object without depending on the method's API. Closes ponylang#1409.
This change provides a way to chain calls on an object without depending on the method's API. Closes ponylang#1409.
This change provides a way to chain calls on an object without depending on the method's API. Closes ponylang#1409.
This was marked closed by #1411, but I'm not sure it took care of the full scope of the RFC. Specifically, I think the remaining work is to revise APIs that return |
@jemc I don't think it is part of the RFC but I was planning to do a PR on that after the method chaining itself was in. I'll open that PR soon. |
Okay, fair enough. I'll close this for now. I suppose an RFC would be a good place to discuss what the best meaningful return values for the changed methods should be, instead of resetting them all to |
Introduce a syntax sugar for invoking a method such that the return value is discarded and replaced with the object itself allowing further operation.
https://github.com/ponylang/rfcs/blob/master/text/0025-sugar-for-method-chaining.md
The text was updated successfully, but these errors were encountered: