|
|
|
|
|
by nyssos
981 days ago
|
|
I'm not using head, because I know Haskell well. But someone new to the language is never, ever, ever going to intuit that you get the head of a list with `listToMaybe` and `head` actually means `unsafeHead` and should almost never be used. > Changing head so that it returns a Maybe breaks code Of course. So did `Applicative`. So did `Foldable` and `Traversable`. So will removing (/=) from Eq, whenever that actually gets merged - and that was imo a far, far less problematic wart than having partial functions in Prelude.
Breaking changes need to be made very carefully and very slowly: simplified subsumption was terribly handled, if not an outright mistake. But refusing to make them at all is how you get C++. |
|
They don't have to. Pattern matching is one of the first things they will learn, so they can use that instead.
> and `head` actually means `unsafeHead` and should almost never be used.
They don't need to intuit it. The next version of base will have a warning on `head` telling them to use a safer alternative instead.
By the way, the Haskell community is currently struggling to accept that it should make fewer breaking changes, in order to become a more stable platform for industry use. We're definitely not going to start breaking more code!