Re:The general value of typed functional programming lies in...
by heartbeats on Monday February 24, 2020 @03:19PM
(#22408006)
C.
[ Parent
| on HN ]
Re:The general value of typed functional programming lies in...
by marcosdumay on Monday February 24, 2020 @04:36PM
(#22408709)
How does that fail at compile time if you try to read a value when there is none?
Re:The general value of typed functional programming lies in...
by madmax96 on Monday February 24, 2020 @04:58PM
(#22408907)
Some of Dawson Engler’s work helps solve this problem, starting around [1]. In that, he shows us how to write custom compiler rules in a high-level language. These rules are sufficient to enforce that maybe type. In another paper, Engler (or one of his several talented students, can’t remember now) shows us how to automatically infer many of these rules.
Re:The general value of typed functional programming lies in...
by heartbeats on Monday February 24, 2020 @05:19PM
(#22409040)
If you try to use it val directly, it fails. You must unpack it first.
To do something like x.get() in Scala when x is empty is a runtime error, not a compile-time error.