feat(scala): add generated grpc service support for scala#3762
Merged
chaokunyang merged 3 commits intoJun 13, 2026
Conversation
pandalee99
approved these changes
Jun 13, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why?
Scala schema generation already emits Scala 3 model types and modules, but schemas with service definitions could not generate Scala gRPC companions. This left Scala users without generated client/server bindings for Fory-encoded gRPC services even though Java, Python, Go, Rust, and Kotlin already support
--grpc.What does this PR do?
foryc --scala_out=... --grpc, including service descriptors, server base classes, generated clients, Fory-backed grpc-java marshallers, unary calls, and streaming method shapes.RpcFutureandRpcIterator, for generated unary and server-streaming client convenience APIs.--grpcoutput creation.Related issues
#3266
AI Contribution Checklist
yes/noyes, I included a completed AI Contribution Checklist in this PR description and the requiredAI Usage Disclosure.yes, my PR description includes the requiredai_reviewsummary and screenshot evidence of the final clean AI review results from both fresh reviewers on the current PR diff or current HEAD after the latest code changes.Does this PR introduce any user-facing change?
User-facing changes:
--grpcservice companion generation and new Scala RPC handle traits used by generated clients.Benchmark