News for hackers. Stuff that matters.
Re:Bracha v Felleisen “Types for an Untyped World” (2015) [v... by rbehrends on Monday May 29, 2017 @12:48PM (#14439999)
> Not really.

Can you provide support for this claim? Existing research [1] seems to indicate that it isn't clear-cut at all.

> Today, we have very good type inference engines and there is really no reason to ever want to use a dynamically typed language.

Type inference has its shares of issues once you're dealing with non-local type inference, subtype polymorphism or parametric polymorphism.

[1] https://danluu.com/empirical-pl/

Re:Bracha v Felleisen “Types for an Untyped World” (2015) [v... by wtetzner on Monday May 29, 2017 @01:05PM (#14440092)
> Type inference has its shares of issues once you're dealing with non-local type inference, subtype polymorphism or parametric polymorphism.

Just wanted to point out that actually, type inference works quite well with parametric polymorphism, like in ML. Even non-local type inference can work fine given other constraints, also like in ML.

Re:Bracha v Felleisen “Types for an Untyped World” (2015) [v... by rbehrends on Monday May 29, 2017 @01:15PM (#14440133)
1. Only for unconstrained parametric polymorphism. For constrained parametric polymorphism, ML requires functors (don't get me wrong, I think ML functors are brilliant, but they do require you to be rather explicit about your typing).

2. I wouldn't say that it's without problems even for unconstrained parametric polymorphism. Consider the value restriction [1] and the fact that if you add subtyping to the mix (as in OCaml), you're getting some really non-trivial issues (as Scala found out the hard way).

[1] http://mlton.org/ValueRestriction

Re:Bracha v Felleisen “Types for an Untyped World” (2015) [v... by wtetzner on Monday May 29, 2017 @01:32PM (#14440258)
Yes, subtyping makes everything more complicated. I think there was a paper about type inference for subtyping posted on HN a while back, but I don't remember much about it.