Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

I like that it’s panic, because it calls out broken places in the model

but yea, great work. it's a lot to figure out.

wrapping my mind around lifetimes in graph::Graph was one of the most challenging parts

...and i guess figuring out how best to use enums too.

&gt; Ok, finally. With #4221 in place, the rust-io branch is faster than v2 in master, and under 2x slower than v1.

and there is a bunch of dumb duplication happening there, so i'm optimistic it can come down further

would it make sense to tear lmdb out of the v2 codebase at this point?

potentially. peiyu was looking at maybe resurrecting it though.

more likely just the in memory part not the lmdb

<https://blog.rust-lang.org/2017/02/02/Rust-1.15.html>

yea, nice. nothing huge, but the cadence is fun.

``` [dependencies]
 crossbeam = "0.2.10"
 fnv = "1.0.5"
-futures = "0.1.10"
-futures-cpupool = "0.1"
+futures = { git = "<https://github.com/stuhood/futures-rs>", branch = "stuhood/add-shared-debug" }
+futures-cpupool = { git = "<https://github.com/stuhood/futures-rs>", branch = "stuhood/add-shared-debug" }```

banging on <https://github.com/alexcrichton/futures-rs/issues/381> =/

<@U054MQUPL> : it looks like there might be an issue with the rust code starting a threadpool pre-daemon, and then getting daemonized