#3339: Data.Monoid: Add (<>) as a synonym for mappend
-----------------------------+----------------------------------------------
Reporter: bos | Owner:
Type: proposal | Status: new
Priority: normal | Milestone: Not GHC
Component: libraries/base | Version: 6.10.3
Resolution: | Keywords:
Testcase: | Blockedby:
Difficulty: Unknown | Os: Unknown/Multiple
Blocking: | Architecture: Unknown/Multiple
Failure: None/Unknown |
-----------------------------+----------------------------------------------
Comment(by jeltsch):
Replying to [comment:25 nominolo]:
> Getting rid of `mappend` would break a ''lot'' of packages, so that will
take a while.
Of course. But that’s why I think we should start to prepare for
{{{mappend}}} removal now. ;-)
> Also, what should happen to `mconcat`? The naming of `mappend` makes
somewhat sense, because `[a]` is the free Monoid, so `mconcat` is just the
extension of that naming strategy. Should `mconcat` stay as is, or can
anyone think of a better name?
I don‘t like the {{{m}}} in {{{mappend}}} and {{{mconcat}}} because it’s
not very descriptive. Sometimes it means “monoid” as in {{{mappend}}} and
{{{mconcat}}}, and sometimes it means “monad” as in {{{mzero}}},
{{{mplus}}}, and {{{msum}}}. So it might be a good idea to change
{{{mconcat}}} to {{{concat}}}, at least in the long run. The current
{{{concat}}} is just {{{mconcat}}} of the {{{[a]}}} instance of
{{{Monoid}}}, so it could just be removed then.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3339#comment:26>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
