SJ
[internal] Adding first-party sources compilation, linking, packaging, and running to the CC backend
> > However, with @tdyas's cgo PR in the mix, it seems like a good time to bikeshed on target and subsystem naming, determining how consistent we want to keep...
Documentation gotcha that I just ran into (maybe a bug?): `rule_helper` function must be declared before usage.. Meaning if you use a `rule` and `rule_helper` in the same file, the...
I should point out that, while it would be nice if order didn't matter - it's not a big deal, assuming it's documented and/or if there was some sort of...
Had this just now. Performing `rm -r .pids .pants.d` and then running my pants command brought colour back to the screen.
> I think you oughta open the can of worms and fish for feedback again on slack. Goal churn was received last time very poorly. Agreed, but I think the...
@Eric-Arellano @benjyw Any thoughts on the outstanding questions? I'm not really sure in which direction I can take this to integrate with Pants. From the Slack conversations, `export` would seem...
Yep, just pushed two fixes: https://github.com/pantsbuild/pants/pull/16442 Works on Mac and Debian Bullseye for me now, no warnings/complaints.
> I'm fine with a long-term alias. And it is worth rethinking the "temporary name while a feature is experimental" [habit]? >> Maybe we should get more cozy with "experimental"...
Just so this isn't fully lost to Slack history (between Stu and I): > So what about doing something more like `--version`? ./pants --completions ? > this would work too...
@stuhood No problem, but we still need an endgame here wrt my Slack thread (https://pantsbuild.slack.com/archives/C0D7TNJHL/p1664221191673119). > However, this leaves me with a couple outstanding questions: > 1. What should the...