had an EVEN BETTER IDEA in https://github.com/pantsbuild/pants/issues/7071#issuecomment-456309997 which can be summarized as "tee the stdout from zinc compiles to a file named `output.txt`":

> ./pants --compile-zinc-workunit-output="+{'stdout': {'output.txt': ['COMPILE']}}" test ::

and the

stdout

corresponds to

workunit.output('stdout')

, but we can extend that to other output types to allow for non-hierarchical output labelling for an asynchronous v2 UI!

I really like the idea of teeing specific workunits’ outputs to specific files/streams(/sockets?), but I’m a bit lost as to how we would extend it to fit the V2 async model. I agree that file write synchronization is relatively easy to fix problem, but I find it hard to imagine the extensions of that command line, could you post an example?

well it would be analogous to the

WorkUnitMessageType

i proposed in comments in the linked issue

Goootcha! Thanks for the explaination, I like the idea!

i can totally dive in more and write code as necessary! am very excited about this but my opinions are highly malleable!