You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Cyclic reference involving val <import> errors still exist #26340
This is a follow-up to #25894 (minimization inc_export_cyclic_err), which was fixed by #25900. The fix breaks the cycle when a single file is recompiled against its siblings' TASTy, but the same cyclic error still occurs when two source units are recompiled together.
#25900 force-completes only the sibling <src>$package classes that come from the classpath (isDefinedInBinary). Here a second source unit, hdl.scala, is recompiled at the same time and re-exports the same givens via a top-level export hdl.*. Because hdl is now a source sibling (not isDefinedInBinary), it is not force-completed, so the export chain through it is resolved lazily during the import's completer and the cycle returns.
Compiler version
3.9.0-RC1 (contains the fix from #25900 / #25894).
Activity
Fixes #26340: Break cross-unit cyclic export across recompiled source…
Fix scala#26340: break cross-unit cyclic export across recompiled sou…
Merge pull request #1233 from scala/backport-lts-3.3-26341
Merge pull request #1247 from scala/backport-lts-3.9-26341