Re:Write Junior Code
by monoideism on Monday December 30, 2019 @12:06AM
(#21910944)
OK, those are poor stylistic practices, but they’re orthogonal to point-free style.
[ Parent
| on HN ]
Re:Write Junior Code
by edflsafoiewq on Monday December 30, 2019 @12:43AM
(#21911084)
It is related. In point-free style the "omitted" parameters have to be distinguished positionally; they have no names at all, not even 'a' or 'b'.
Re:Write Junior Code
by monoideism on Monday December 30, 2019 @10:52AM
(#21914120)
> In point-free style the "omitted" parameters have to be distinguished positionally; they have no names at all, not even 'a' or 'b
Yes, that's literally the definition of point-free style.
I was referring to labeling function parameters `a` and `b`.
Also, when I checked, that's actually not what the FGL library does. It labels type parameters with `a` and `b`. Labeling generics and type parameters with letters of the alphabet is pretty typical for a wide range of languages (ie, `T` in Java, etc.). Arguably, it's a bad idea, but it's by no means unique to Haskell.
^^^^^ This is extremely insightful, and now ranks as the most accurate and succinct explanation I've seen of why point-free is terrible.
Re:Write Junior Code
by monoideism on Monday December 30, 2019 @11:01AM
(#21914209)
It's not extremely insightful. It's literally the definition of point-free style.
Also, Haskell doesn't have labeled/keyword function parameters, regardless of whether or not you use point-free style. Sometimes, people pass in a record to achieve a similar effect, but in general, passing in a ton of parameters goes against idiomatic Haskell style.