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 think its `chunks` still gives you references

But either way, Bytes looks like it will make me happy :slightly_smiling_face: Will play with it shortly!

Definitely looks like a thing I would like to be in the core of the language

as with all buffer types, it's a bit fidgety.

<@U06A03HV1> Done in <https://github.com/pantsbuild/pants/pull/5293> - very nice :slightly_smiling_face: Now tempted to go around swapping Bytes into a few places… Anywho, wanna take a look before I merge? :slightly_smiling_face:

there is a way to make it a bit faster by taking advantage of the potential mutability of Bytes

Oh? As in, avoiding the copy entirely, and popping off slices, rather than using slices as views?

Cool :slightly_smiling_face: Excited to do that, but will do it as a separate PR because it’s a pretty invasive change

Wow. Apparently empty lines in rustdoc are strongly forbidden, and if you use them, the compiler will panic, and that’s working as intended.

<https://github.com/rust-lang/rust/issues/47323>

Hmm… Been seeing some flakiness on travis downloading rust toolchains: <https://travis-ci.org/pantsbuild/pants/jobs/327273910>

<@U066LC126>: it just occurred to me that we can statically determine whether variants should be propagated in a particular path

updated <https://github.com/pantsbuild/pants/issues/4020>

... i think that makes them totally feasible again, which is exciting. was worried.

lmk if anyone has any ideas on: <https://github.com/pantsbuild/pants/issues/5174>

doesn’t solve for the echo case afaict when used on either end

the crux is we need to be putting the thin clients terminal driver into certain modes from the context of the forked pantsd-runner’s subprocess’d repl

or supplying our own mode impl on top of a raw tty

So I guess the canonical examples of how to do this  are provided by tmux and screen