11–20 of 188 posts
Ask five programmers to define functional programming, get fifteen different answers.
Most people would agree that in functional programming we can pass functions around as first class objects. What we disagree on is the definition of function.
Ask five programmers to define functional programming, get fifteen different answers.
I always thought FP == pure functions. I guess not?
Earlier quoted context omitted.
Most people would agree that in functional programming we can pass functions around as first class objects. What we disagree on is the definition of function.
That's just one aspect of functional programming. By that definition, almost any modern language is functional.
Ask five programmers to define functional programming, get fifteen different answers.
Ask five programmers to define functional programming, get fifteen different answers.
To me the core is "no side effects" though (for pure FP). It's interesting to see what others consider to be the most salient feature(s).
let persons = names
.map(Person.init)
.filter { $0.isValid }
var persons: [Person] = []
for name in names {
let person = Person(name: name)
if person.isValid {
persons.append(person)
}
}
I'm curious, does every else find this let persons = names .map(Person.init) .filter { $0.isValid } easier to read than this? var persons: [Person] = [] for name in names { let person = Person(name: name) if person.isValid { persons.append(person) } } I understand and appreciate the value of compact code, but I find the first one harder to read. A lot of inferred/token based coding is harder for me to mentally parse.
let persons = [ p | n I'm curious, does every else find this let persons = names .map(Person.init) .filter { $0.isValid } easier to read than this? var persons: [Person] = [] for name in names { let person = Person(name: name) if person.isValid { persons.append(person) } } I understand and appreciate the value of compact code, but I find the first one harder to read. A lot of inferred/token based coding is harder for me to mentally parse.
It also depends on the language obviously. In this example, the first example has special tokens for the filter. It doesn't have to be so.
I'm curious, does every else find this let persons = names .map(Person.init) .filter { $0.isValid } easier to read than this? var persons: [Person] = [] for name in names { let person = Person(name: name) if person.isValid { persons.append(person) } } I understand and appreciate the value of compact code, but I find the first one harder to read. A lot of inferred/token based coding is harder for me to mentally parse.
When it's optional, well, sadness ensues.
I'm curious, does every else find this let persons = names .map(Person.init) .filter { $0.isValid } easier to read than this? var persons: [Person] = [] for name in names { let person = Person(name: name) if person.isValid { persons.append(person) } } I understand and appreciate the value of compact code, but I find the first one harder to read. A lot of inferred/token based coding is harder for me to mentally parse.
The other thing is that experience brings the ability to track what's going on. The formulation of the answer here is probably new to you. As you get use to this, or Streams for Java, or threading for Clojure, etc, you'll understand it by default.