Support custom grain call return types #8415
Merged
Conversation
This file contains 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR adds support for extending the set of supported grain return types.
This allows us to support calling patterns beyond request-response. For example,
IAsyncEnumerable<T>.A subsequent PR will add initial support for returning
IAsyncEnumerable<T>from grains, based on this functionality.To use this, a developer would start by annotating a request base type with
[ReturnValueProxy(initializerMethodName)]. Doing so prevents the code generator from relying on .NET'sAsyncMethodBuilderto create the instances of the return type and instead allows the value returned from the method with the name specified byinitializerMethodNameto provide that value.Microsoft Reviewers: Open in CodeFlow