Skip to content

[RPC] Split RPC API for sync and async to have explicit return types #24247

New issue
New issue
Closed
Closed
[RPC] Split RPC API for sync and async to have explicit return types#24247
Assignees
xush6528rohan-varma
Labels
module: rpcRelated to RPC, distributed autograd, RRef, and distributed optimizeroncall: distributedAdd this issue/PR to distributed oncall triage queuetriagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate module
@mrshenli

Description

@mrshenli
mrshenli
opened on Aug 13, 2019

As pointed out by @aazzolini in #23569, instead of using an async_call arg to distinguish sync and async RPC, we should split it into different sync and async APIs, so that we can have explicit return type hints.

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera

Metadata

Metadata

Assignees

Labels

module: rpcRelated to RPC, distributed autograd, RRef, and distributed optimizeroncall: distributedAdd this issue/PR to distributed oncall triage queuetriagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate module

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions