RFR 8155674: Move javac towards a "by-file" compilation policy

Liam Miller-Cushon cushon at google.com
Fri Dec 2 02:18:31 UTC 2016

On Thu, Dec 1, 2016 at 6:06 PM, Jonathan Gibbons <
jonathan.gibbons at oracle.com> wrote:

> Does this address the potential problem with cycles that you mentioned in
> the original email?

Not fully. It improves the current behaviour by ensuring files always go
through attr and flow as a unit, but classes may still be desugared
separately from their compilation unit.

One of the test cases has compilation units [One, Two] and [Three, Four],
where Two extends Four, and Three extends One. There's no way to linearize
that so supertypes are desugared first and files are desugared as a unit.

Are there still plans to remove the ordering constraint in TransTypes?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/compiler-dev/attachments/20161201/c627af72/attachment.html>

More information about the compiler-dev mailing list