- User Since
- Apr 18 2019, 7:59 AM (51 w, 2 h)
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.
I had to squint hard at the c code to find any discrepancy, of which there seems to be none.
Fri, Apr 3
This series is great.
Aside from the outdated futures and Rust edition that Yuya already said are temporary, this looks good!
Shouldn't this be merged with the previous change?
(I'll be re-pasting all of my comments that got lost in emails for this series)
Tue, Mar 31
Wed, Mar 25
Could you add a comment about what happens if you hg split either the base or the tip of the range?
I am very curious as to how the UI will look on a folded series.
Tue, Mar 24
Mon, Mar 23
Fri, Mar 20
Thu, Mar 19
Wed, Mar 18
Tue, Mar 17
Mon, Mar 16
Fri, Mar 13
This seems like something that can easily have a few simple unit tests