-
-
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
Method chaining (RFC #25) #1411
Conversation
Woo hoo! |
Is there documentation updates with this? Tutorial changes for example? I dont think we should merge wo corresponding documentation being ready. |
The RFC says this:
|
Can we get some compiler tests that demonstrate the compiler errors received when you get the caps wrong? That is, we have compiler tests for constructs like automatic receiver recovery that show/prove which kinds of situations where the receiver can or can't be recovered. I think having some similar tests in place for the new semantics of this change will be pretty critical. |
@jemc I'll add that. |
@Praetonus that tutorial update is in the works? |
@SeanTAllen Yes, I'll do a PR. |
Tests added. |
Tutorial PR submitted: ponylang/pony-tutorial#167 |
This change provides a way to chain calls on an object without depending on the method's API. Closes ponylang#1409.
I've fixed an assertion check that was wrongly considering |
This change provides a way to chain calls on an object without depending on the method's API.
Closes #1409.