4 ms·
Why's that?
by bigbillheck 3y ago
Why's that?
- switchbak 3y agoTypes interop on a VM that wasn't designed for a more complex one like Scala has. Collections interop between Java<->Scala. Scala's (immutable/mutable) collections are not built on the Java ones, and they provide helpers to translate between the two. Calling conventions, name mangling, Java to Scala issues, etc.
- fulafel 3y agoFP doesn't need complex type systems though. And there's not a lot of type stuff on the JVM level, it's more dynamic than you'd think.
- switchbak 3y agoI’m not defending Scala design just describing the interop challenges given said design. Scala was certainly envisioned with a strong type system in mind. The JVM doesn’t mandate mandate that, true, but the compiler they wrote did.