scalac compilation currently uses transitive dependencies, unlike java. javac uses only direct dependencies because of export types: https://blog.pantsbuild.org/automatically-unlocking-concurrent-builds-and-fine-grained-caching-on-the-jvm-with-dependency-inference/#exporttypes … which we haven’t implemented for scala yet (https://github.com/pantsbuild/pants/issues/13836)

for example: File A:

object A {
  def a(x: Int): Int = ???
}

File B:

import A

object B extends A {
  
}

File Main:

import B.a

def main() = println(a(5))

the above won't compile at the moment, because pants scala-parser cannot find the symbol

B.a

while the producer of the symbol could be made recursive, the consumer could also be made more lenient… by essentially declaring a dependency on both

B.a

and

B

when it encounters

B.a

but… yea, actually. having

class

or

object

declare themselves as recursive probably makes sense? they own that namespace. but that seems quite similar to not having symbol level awareness… Java doesn’t currently: https://github.com/pantsbuild/pants/issues/13765 . i’d need to page back in why we felt that symbol level awareness was necessary in the first place.