-
Notifications
You must be signed in to change notification settings - Fork 52
Add @endpoint(explicit_response_port=True) #634
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
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This option exposes an option that rust actors have always had to get the response port as an argument instead of using the return value of the function as the response. Having this feature allows synchronous actors to defer responding to a message and process other messages, making them as expressive as asynchronous actors which accomplished this by awaiting. Enjoy the giant @overload copypasta to appease the python typecheckers. Differential Revision: [D78901486](https://our.internmc.facebook.com/intern/diff/D78901486/) [ghstack-poisoned]
This was referenced Jul 24, 2025
zdevito
added a commit
that referenced
this pull request
Jul 24, 2025
This option exposes an option that rust actors have always had to get the response port as an argument instead of using the return value of the function as the response. Having this feature allows synchronous actors to defer responding to a message and process other messages, making them as expressive as asynchronous actors which accomplished this by awaiting. Enjoy the giant overload copypasta to appease the python typecheckers. Differential Revision: [D78901486](https://our.internmc.facebook.com/intern/diff/D78901486/) ghstack-source-id: 298325270 Pull Request resolved: #634
This pull request was exported from Phabricator. Differential Revision: D78901486 |
This option exposes an option that rust actors have always had to get the response port as an argument instead of using the return value of the function as the response. Having this feature allows synchronous actors to defer responding to a message and process other messages, making them as expressive as asynchronous actors which accomplished this by awaiting. Enjoy the giant overload copypasta to appease the python typecheckers. Differential Revision: [D78901486](https://our.internmc.facebook.com/intern/diff/D78901486/) [ghstack-poisoned]
zdevito
added a commit
that referenced
this pull request
Jul 24, 2025
Pull Request resolved: #634 This option exposes an option that rust actors have always had to get the response port as an argument instead of using the return value of the function as the response. Having this feature allows synchronous actors to defer responding to a message and process other messages, making them as expressive as asynchronous actors which accomplished this by awaiting. Enjoy the giant @overload copypasta to appease the python typecheckers. ghstack-source-id: 298374454 @exported-using-ghexport Differential Revision: [D78901486](https://our.internmc.facebook.com/intern/diff/D78901486/)
This option exposes an option that rust actors have always had to get the response port as an argument instead of using the return value of the function as the response. Having this feature allows synchronous actors to defer responding to a message and process other messages, making them as expressive as asynchronous actors which accomplished this by awaiting. Enjoy the giant overload copypasta to appease the python typecheckers. Differential Revision: [D78901486](https://our.internmc.facebook.com/intern/diff/D78901486/) [ghstack-poisoned]
zdevito
added a commit
that referenced
this pull request
Jul 26, 2025
Pull Request resolved: #634 This option exposes an option that rust actors have always had to get the response port as an argument instead of using the return value of the function as the response. Having this feature allows synchronous actors to defer responding to a message and process other messages, making them as expressive as asynchronous actors which accomplished this by awaiting. Enjoy the giant @overload copypasta to appease the python typecheckers. ghstack-source-id: 298820920 @exported-using-ghexport Differential Revision: [D78901486](https://our.internmc.facebook.com/intern/diff/D78901486/)
This pull request was exported from Phabricator. Differential Revision: D78901486 |
This option exposes an option that rust actors have always had to get the response port as an argument instead of using the return value of the function as the response. Having this feature allows synchronous actors to defer responding to a message and process other messages, making them as expressive as asynchronous actors which accomplished this by awaiting. Enjoy the giant overload copypasta to appease the python typecheckers. Differential Revision: [D78901486](https://our.internmc.facebook.com/intern/diff/D78901486/) [ghstack-poisoned]
zdevito
added a commit
that referenced
this pull request
Jul 26, 2025
Pull Request resolved: #634 This option exposes an option that rust actors have always had to get the response port as an argument instead of using the return value of the function as the response. Having this feature allows synchronous actors to defer responding to a message and process other messages, making them as expressive as asynchronous actors which accomplished this by awaiting. Enjoy the giant @overload copypasta to appease the python typecheckers. ghstack-source-id: 298823614 @exported-using-ghexport Differential Revision: [D78901486](https://our.internmc.facebook.com/intern/diff/D78901486/)
This pull request was exported from Phabricator. Differential Revision: D78901486 |
This pull request has been merged in e305336. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stack from ghstack (oldest at bottom):
This option exposes an option that rust actors have always had to get the response port as an argument instead of using the return value of the function as the response.
Having this feature allows synchronous actors to defer responding to a message and process other messages, making them as expressive as asynchronous actors which accomplished this by awaiting.
Enjoy the giant @overload copypasta to appease the python typecheckers.
Differential Revision: D78901486