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

Pants

<@U054MQUPL> - wondering if any progress on <https://github.com/pantsbuild/pex/pull/399>

<@U054MQUPL> I filed a ticket for the pants server issue I noticed. lmk if I can provide more info <https://github.com/pantsbuild/pants/issues/5140>

<@U06A03HV1> So, strict_deps + exports is sort of like adding intransitive to all of the dependency edges that are not exported, but only for the compile scope. Looking at that has got me wondering if we could reimplement strict_deps as an adjustment to the closure predicate code.

Unfortunately, I convinced Garrett to implement intransitive as a vertex property, rather than an edge property =p

well, we don’t have edge properties as yet either

<@U066LC126>: but, a reminder that basically the next thing i'm going to be working on is porting jvm_compile to the new engine.

(hmm... the first line is a lie. tests will likely be first)

So, how are you planning on dealing with the graph traversal issues? Maybe we could come up with something that isn’t immediately stale

<@U066LC126>: for one thing, there won't be a `BuildGraph` to traverse.

<@U066LC126>: but i suspect it will involve requesting either: `SelectDependencies(TransitiveClasspath, HydratedTarget)`, or `SelectDependencies(StrictClasspath, HydratedTarget)`

the scopes thing has got me thinking that rather than Strict/Transitive, the engine would have CompileClasspath and RuntimeClasspath. I have to think about that some more though

<@U066LC126>: i think transitive vs intransitive is the fundamental thing, and then scopes would be applied by walking the output

but whether something is transitive or intransitive depends on the scope

<@U066LC126>: no... it depends on what the caller wants

well, sorry... not "no": rather "the way i've been thinking about it is"

oh, so there’d be a strict_compile which consumes strict type attributed source file declarations and requests strict classpaths for them

and a transitive_compile for non-strict compilation units

and those would request different types of classpaths

<@U066LC126>... er... i'm not entirely sure how the recursion works here.

but, this will be recursion, memoized in the graph.

at each node, there will be a `SelectDependencies` to request the next level