Re: Proposal: Add Data.Semigroup to base, as a superclass of Monoid

There are two significant changes proposed here: Add Data.Semigroup to base Make Monoid a subclass of Semigroup Perhaps a smoother path would be to first add Semigroup to base (minimal impact on existing code), then make Monoid a subclass at a later date? The advantages of this are: People will stop reinventing the NonEmpty wheel, because they don't know it exists or isn't worth creating a new dependency for. Adding a package to base is much less intrusive than changing the hierarchy of an existing class.. -- View this message in context: http://haskell.1045720.n5.nabble.com/Proposal-Add-Data-Semigroup-to-base-as-... Sent from the Haskell - Libraries mailing list archive at Nabble.com.