Again, so long as SomeClass and the late-implement...
# language-proposalsb
benleggiero
08/29/2017, 11:34 PMAgain, so long as SomeClass and the late-implemented interface are in the same project, I don't see the problem. Just resolve them before they become bytecode
d
dmitry.petrov
08/30/2017, 4:56 AMThen it's a "partial class". If we would do that (not quite sure), it's better to make "partiality" of the class explicit - that is, add a soft keyword modifier that would allow splitting class declaration into multiple declarations possibly in different files. In fact, we already have something close, but it is buried deep inside Java interoperability magic for stdlib (multifile classes).
There's one issue with partial classes on JVM I can think of right now: class file has a single source file, so, some additional hacks with source maps (similar to those used for the inline functions) would be required for debugging and exceptions.
Initialization order may be complex (and that's probably the main reason NOT to have partial classes, depends on who you ask)
🤔 1