I am very happy to see this paper. It was an enjoyable read, and accessible to non-experts such as myself. I appreciated the effort spent on research, and was even happier to see that you have started implementing these suggestions and have a plan going forward. Technical debt is a hard thing to overcome, especially in the face of a rapidly evolving language.
This paper resonates with me as both a user and one-time (as in a single time🙂) developer of GHC. As a user, I’ve run into issues related to the debts you discuss. I also tried to fix a GHC bug, and remember being overwhelmed by DynFlags. I applaud your efforts. Thank you for this service to the Haskell community. Eric Crockett On Wed, May 4, 2022 at 3:51 AM Sylvain Henry <sylv...@haskus.fr> wrote: > Hi GHC devs, > > With John Ericson and Jeffrey Young we wrote a paper about the > modularization of GHC. It gives a global picture for the refactorings we > have been performing (c.f. e.g. #17957) and some potential future ones. > > Announce blog post: > https://hsyl20.fr/home/posts/2022-05-03-modularizing-ghc-paper.html > Paper: https://hsyl20.fr/home/files/papers/2022-ghc-modularity.pdf > Discussion on Reddit: > https://www.reddit.com/r/haskell/comments/uhdu4l/modularizing_ghc_paper/ > > We welcome any feedback, here or on reddit. > > Cheers, > Sylvain > > _______________________________________________ > ghc-devs mailing list > ghc-devs@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs >
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
