typesafety

5 ms·

1.
by typesafety 15y ago
I would like them to be fixable, because otherwise Scala is a decent language, but it is too early to say.
2.
by typesafety 15y ago
Good one.
3.
by typesafety 15y ago
I'm guessing you've never actually proven type safety for a non-trivial language, if any. While there are many ways type safety could be stated for Scala, I'm pretty sure most Scala programmers would like the version of type safety that st
4.
by typesafety 15y ago
I guess I'm not following, because type safety is a property of typed language. Expressive power is orthogonal. There are type systems that are more expressive and less expressive and ideally you design your language so that regardless of
5.
by typesafety 15y ago
I don't see any mention of a specific safety problems. Plus, I am given to believe that there are actually numerous papers on the extensions involved in the Haskell type system. Consider http://haskell.org/haskellwiki/Simonpj/Talk:Outsid
6.
by typesafety 15y ago
I didn't find these bugs, they're just ones that have been accumulating over the years. If all of these were as simple as being "bugs" rather than flaws in the type system why wouldn't they have been fixed by now? Is there something wrong
7.
by typesafety 15y ago
So I'm curious, can you point to known problems with Haskell or ML that do not involve using the unsafe features? Scala has problems even without resorting to "unsafe" features like casting or native methods.
8.
by typesafety 15y ago
That's really a different issue than type safety.
9.
by typesafety 15y ago
https://lampsvn.epfl.ch/trac/scala/ticket/963 https://lampsvn.epfl.ch/trac/scala/ticket/2856 among others
10.
by typesafety 15y ago
There are numerous holes in the type system. Just browse their bug tracker to see. And several of them are not just "bugs" but deep flaws in the type system.
11.
by typesafety 15y ago
I find it incredibly ironic that they have called the company Typesafe when type-safety is something Scala definitely does not have.