Test case suggested by @tuotuo: rank an interface-heavy codebase, not an import-heavy one. Exposed (JetBrains Kotlin SQL, 2k files): Table.kt #1 — 238 files depend on it, 2.3k LOC. And the DAO layer holds a real 2-file cycle: EntityClass <-> EntityNotFoundException imports each other, the exception carries the entity as a field type. Interface-heavy ranking lands on the core abstractions, exactly where the blast radius is.
https://codeberg.org/beheej/breakpoint
#kotlin #devtools