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

Pants

Ok, so vaguely a Stat is an inode, and a PathStat is a dirent?

so `Stat` is a reasonable name... `PathStat` is a confusing name.

not sure about the latter bit... I don't think PathStat has a unix equivalent

it's a pair of the input to realpath, and the output, essentially.

<@U054MQUPL>: the workflow with the daemon is looking really nice.

as an anecdote in support of the "continuous re-try" case, when i need to fix errors in a list of targets, i do something like this:

```for target in ${TARGETS[*]}; do
  echo -e "\n\n$target\n\n"
  while ! ./pants compile $target ; do
    echo -e "\n\n...retrying...\n\n"
  done
done```

...with just the daemon, it's surprisingly usable

yeah, the latest round of cleanups is looking real good

I feel like we could provide a tool for the continuous retry case

and ship that in like 1-2 days as a sidecar thing

can goal names contain tildes? `./pants ~run`?

`~run` turns into `/Users/run` in bash if user "run" exists

would be good to actually spend some time designing it. if what we eventually want to do with it is already easy to do, then could do something cleaner.

the pitfall i guess would be introducing new syntax or flags, and then realizing later that they don't work with <https://github.com/pantsbuild/pants/issues/4769>

does "not working with" mean "forcing more eager evaluation than necessary" ?

... i guess that's the worst case... maybe? i can't think of a worse case.

<@U06A03HV1> Any idea how to resolve this?

```
    |          ^^^^^^^ a collection of type `std::vec::Vec&lt;std::boxed::Box&lt;futures::Future&lt;Item=bazel_protos::remote_execution::DirectoryNode, Error=std::string::String&gt;&gt;&gt;` cannot be built from an iterator over elements of type `std::boxed::Box&lt;futures_cpupool::CpuFuture&lt;bazel_protos::remote_execution::DirectoryNode, std::string::String&gt;&gt;`
    |
    = help: the trait `std::iter::FromIterator&lt;std::boxed::Box&lt;futures_cpupool::CpuFuture&lt;bazel_protos::remote_execution::DirectoryNode, std::string::String&gt;&gt;&gt;` is not implemented for `std::vec::Vec&lt;std::boxed::Box&lt;futures::Future&lt;Item=bazel_protos::remote_execution::DirectoryNode, Error=std::string::String&gt;&gt;&gt;`
```

I would naively assume that assume a CpuFuture&lt;X, Y&gt; and a Future&lt;Item=X, Error=Y&gt; were compatible