Difference between revisions of "Nitpicks"
Jump to navigation
Jump to search
m (Added category Proposals) |
|||
Line 1: | Line 1: | ||
[[Category:Language]] |
[[Category:Language]] |
||
+ | [[Category:Proposals]] |
||
This page is for people to record nitpicks about the Haskell language. |
This page is for people to record nitpicks about the Haskell language. |
Revision as of 09:41, 20 August 2015
This page is for people to record nitpicks about the Haskell language.
A "nitpick", in this case, is something that is annoying or could be improved, but is probably not important enough to justify the added complexity of tacking it on as an extension or breaking existing code.
In other words, if we could go back in time and fix it before it happened, we probably would, but now it would probably be too onerous.
Ideally, these nitpicks could help to inform future proposals or compatibility-breaking changes to the language. Even if they may be too onerous to change right now, it's possible that it would make sense to address them at some other time.
If the nitpick has been discussed at length, please post a link to the discussion.
- Re-naming
data
,newtype
, andtype
. See https://mail.haskell.org/pipermail/haskell-cafe/2015-August/120724.html . - Not having special if-then-else syntax; see https://wiki.haskell.org/If-then-else .
- Re-naming
fmap
tomap
. This has been discussed at length; see http://stackoverflow.com/questions/6824255/whats-the-point-of-map-in-haskell-when-there-is-fmap/6824333 and https://mail.haskell.org/pipermail/haskell-prime/2006-August/thread.html - Cutting up
Num
, which is a mess of various operations one may not want to all define on some type; for example(+)
makes sense for vectors in ℝ³ but(*)
doesn't.