Why base library changes are only discussed on GHC issue tracker and not on the libraries@ list?

chessai chessai1996 at gmail.com
Wed Jul 7 17:52:24 UTC 2021


FWIW, I do believe that changing Show @String needs to be discussed on the
list and I pinged the proposer to do so.

The ByteArray change was in my/Andrew Martin's opinion that it was
straightforward and sensible enough to not need the mailing list. As has
been pointed out by Oleg, on the library submissions page, not all changes
to any core library need to be discussed on the mailing list, as that would
be a gross inefficiency and waste of time. Issue trackers are better, with
escalation when necessary.


On Wed, Jul 7, 2021, 10:12 Oleg Grenrus <oleg.grenrus at iki.fi> wrote:

> For example
>
> - https://gitlab.haskell.org/ghc/ghc/-/issues/20044 ByteArray migration
> from primitive to base
> - https://gitlab.haskell.org/ghc/ghc/-/issues/20027 Changing Show String
> behavior
>
> Why they are discussed "in private", I thought libraries@ list is where
> such changes should be discussed.
>
> - Oleg
>
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20210707/5081e987/attachment.html>


More information about the ghc-devs mailing list