Buy-in for technical proposal 47 which affect GHC devs

Carter Schonwald carter.schonwald at gmail.com
Wed Mar 22 03:18:37 UTC 2023


i mean exactly the hidden status which means you cant directly go to the
highlighted source.

My recollection is that the only justification for that was as a mechanism
for "foot cannons here," which itself predates the more modern *.Internal
module norms we hew to today.

On Tue, Mar 21, 2023 at 8:21 PM Ben Gamari <ben at well-typed.com> wrote:

> Carter Schonwald <carter.schonwald at gmail.com> writes:
>
> > Would this include making those modules not hidden in ghc base? There’s
> > been a few times where that status made it quite hard to build
> > documentation for those modules!
> >
> What do you mean concretely? In most cases modules would remain exposed
> (that is, importable). However, I doubt there will be any change in
> their Haddock status (e.g. not-home or hidden).
>
> Cheers,
>
> - Ben
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20230321/afd68317/attachment.html>


More information about the ghc-devs mailing list