-
Notifications
You must be signed in to change notification settings - Fork 204
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
Upgrade json-transport to Tokio 0.2 #263
Conversation
Thanks for doing this! Have you talked to the maintainers of tokio serde json to see if they'll upstream your changes? |
6e7a4cd
to
ed289dc
Compare
I have! tokio-serde has been upstreamed, tokio-serde-json is under review. |
ed289dc
to
e38fb77
Compare
411e354
to
cfa175a
Compare
I checked with Carl on the tokio-serde-json PR -- he said he's not maintaining the repo anymore. What do you want to do? I say let's just inline the code into tarpc-json-transport; it's less than 200 LOC. |
I'm strongly against inlining since that code is too general for tarpc and can be used elsewhere. I'd be happy to take over and make a release though. |
Do you want to fork and publish a new version? |
cfa175a
to
9b1af92
Compare
9b1af92
to
c9297d4
Compare
Let's get this merged! |
I am temporarily using git version of
tokio-serde-json
, until a newer version is released.