Too Long; Didn't Read
In the last few weeks, we’ve taken a good look at GHC. <a href="https://mmhaskell.com/blog/2018/6/11/contributing-to-ghc-1-preparation" target="_blank">We started</a> by looking at the steps we would need to prepare our local machine for GHC development. This was an especially difficult process on Windows, so we focused there. After that, we looked at the basic way of <a href="https://mmhaskell.com/blog/2018/6/18/contributing-to-ghc-2-basic-hacking-and-organization" target="_blank">creating a development cycle</a> for ourselves. We validated that by changing an error message and seeing how it appeared in the compiler. <a href="https://mmhaskell.com/blog/2018/6/25/contributing-to-ghc-3-hacking-syntax-and-parsing" target="_blank">Last week</a>, we made some more complicated changes. This week, we’re going to wrap this series up by looking at some basic ways of making contributions.