D8383: rust-chg: update name of the server process

Alphare (Raphaël Gomès) phabricator at mercurial-scm.org
Wed Apr 8 08:47:42 UTC 2020


Alphare added a comment.
Alphare accepted this revision.


  > For (d) [modernizing the codebase],  we'll probably want to switch to async-std, but I'm thinking of
  > upgrading to Tokio 0.2 as an intermediate step since process API isn't
  > ported to async-std yet. I'm pretty sure future migration to async-std
  > will be painless compared to the mass rewrite from futures-0.1 to 0.3.
  
  That seems reasonable indeed.
  
  There is also a potentially interesting project we need to keep an eye out for, since it's made by the same person that started `async-std` in the first place: https://stjepang.github.io/2020/04/03/why-im-building-a-new-async-runtime.html. I have to admit that the constant rewrites of async runtimes (or lack thereof) does not help when making a decision and are not really reassuring, but I guess it's a new-ish problem in the Rust ecosystem.

REPOSITORY
  rHG Mercurial

CHANGES SINCE LAST ACTION
  https://phab.mercurial-scm.org/D8383/new/

REVISION DETAIL
  https://phab.mercurial-scm.org/D8383

To: yuja, #hg-reviewers, Alphare
Cc: Alphare, mercurial-devel


More information about the Mercurial-devel mailing list