News for hackers. Stuff that matters.

A comment on The Problem with F# Evangelism. Parent comment

Re:The Problem with F# Evangelism by earthtolazlo on Wednesday August 16, 2017 @02:05PM (#15029681)
That's something addressed by static typing though. I'm pretty sure any dynamic language has that issue, functional or not.
[ Parent | on HN ]
Re:The Problem with F# Evangelism by tome on Wednesday August 16, 2017 @07:17PM (#15032173)
It's fair to say that the boundaries of "functional programming" are pretty amorphous and I certainly didn't mean untyped functional programming. In any case, if you want to prevent null/None errors in a way that gives the programmer his/her own access to create similar new abstractions then you need

* sum types

* parametric polymorphism

* pattern matching

at which point you may as well also add

* first class functions

and then if you don't describe your language as "typed functional" then how do you describe it?

[ Parent | on HN ]