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

Pants

you think you don’t need an allocation, so you gc it, but something else still has a pointer into it

so maybe the `gc` helper is a mismatch then

in this case, deallocating in a `finally` at the end might make it clearer? but it wouldn't prevent the cdata object from dangling*. it's a pointer

it’d also have the effect of explicitly timing the call

so it would be easier to see in debugging

it'll still be called at the end of the function, iirc

fair, it still would only cause issues if something wrote to the place where it was allocated

<https://github.com/bazelbuild/rules_rust>

the rust guys are really taking it seriously: <https://github.com/rust-lang/rust-roadmap/issues/12>

we need another intern to implement rust for pants :stuck_out_tongue:

gotta get v2 solid on some other language

note: should ping `@dyoung` when we're ready for beta testers

&gt; The most fundamental operation exposed to users is now "get me a Snapshot for these PathGlobs"... ie, "get me a fingerprinted tarball of the files matching these globs". This change had two goals: 1) to make the API boundary between rust and python thin, 2) to prepare for remote execution of tasks by capturing inputs into atomic shippable units.

<@U054MQUPL> : maybe we rename <https://github.com/pantsbuild/pants/milestone/6> and target it at "daemon-by-default beta"?

but daemon by default is the important bit

ok, renamed and tweaked: <https://github.com/pantsbuild/pants/milestone/6>