News for hackers. Stuff that matters.
Re:I think I've solved the Haskell records problem by mightybyte on Tuesday January 20, 2015 @10:15PM (#8921259)
Having looked into Ceylon and thought about this a little more...

Ceylon's subtyping is the big thing that is coming to mind right now that makes me prefer Haskell's type system. The purpose of a type system in my mind is to prevent bad programs from being written. But when you combine subtyping with generics you get a problem. Nothing keeps you from looking for an Employee in a Set<Int> because both Employee and Int are a subtype of Object and the covariant use of Set<Int> can be promoted to Set<Object>. But that's a nonsensical thing to do and should obviously be a type error. This kind of thing comes up a lot in practice and is a place where Haskell's type system is safer.

Re:I think I've solved the Haskell records problem by RivieraKid on Thursday January 22, 2015 @07:41AM (#8928833)
This shouldn't be a problem I think. There's not a reason to cast to Set<Object> and then look for employees there. If a function wants to accept a set of let's say emplpyees and ints, it would have a Set<Int|Employee> argument.