Scala is a wonderful language, but I wonder how could be improved if it had it's own runtime?
I.e. what design choices were made because of JVM choice?
views:
761answers:
3Note to self: that list of types is detailled (with links) in http://stackoverflow.com/questions/3112725/advantages-of-scalas-type-system/3113741#3113741
VonC
2010-06-26 15:30:02
+16
A:
This article is a discussion with Martin Odersky (Scala's creator) and includes the compromises that were made in Scala for compatibility with Java. The article mentions:
- Static overloading of methods
- Having both traits and classes
- Inclusion of
nullpointers.
Ben Lings
2010-04-21 18:33:41
+2
A:
Less an issue with the runtime than a cultural hangover: universal equality, hashing, toString.
More deeply tied to the VM: strict by default evaluation, impure functions, exceptions.
retronym
2010-04-23 16:33:22
+1 for universal equality and hashing. What's wrong with universal `toString`?
missingfaktor
2010-04-23 19:53:13
1) It's easy to accidentally display `Object#toString` to a user. 2) `Collection[A]#toString` is inflexible in the way it displays elements of type `A`. See `scalaz.Show` for a alternative.
retronym
2010-04-23 21:23:13