- User Since
- Jun 28 2017, 6:02 PM (206 w, 5 d)
Dec 15 2017
Dec 7 2017
Dec 6 2017
Nov 22 2017
Hm, on second thoughts, does BufReader<BufWriter<File>> actually work? Suspect not.
I think the encode/decode should be factored out more, but I'll leave that up to you.
Nov 17 2017
I stopped following the code around PathRecurse handling - I assume its implementing a chunk of Mercurial-defined logic.
Nov 16 2017
Nov 15 2017
Nov 14 2017
I couldn't find any existing unit tests to update.
Nov 2 2017
Oct 13 2017
Oct 10 2017
Getting more fancy, you could define VLQEncode/VLQDecode traits, then implement them for u64 and i64 (with zigzag), and perhaps other integer types if it makes sense/is useful.
Sep 22 2017
Sep 18 2017
I don't have any particular opinion about which Python binding to use - they all seem a bit rough. I think there's some interesting scope for doing things like using custom derive to automate converting between Rust and Python representations, and iterators/futures/generators to do the conversions of large structures lazily.