Tuples and curried functions are nice for toys, but they are industrial Haskell's worst enemy. If you're going to be able to jump into a big repo and understand stuff, you need to see record field names.
In Python you can add a new named parameter to a function and give it a default value so that you can refactor without changing all the call sites. You can do this in Haskell as well... but not if the parameter set is curried. Come on, don't write software in Haskell that is worse than Python! You can do better
@chris__martin It's way too easy to fall into the trap of adding yet another positional parameter to a function, rather than taking the effort of refactoring to a record.
A library that has been greatly improved by the use of records is Servant. Trying to define a big REST API without NamedRoutes seems like a chore.
Add comment