GHC: Making It Commercially Relevant

GHC has a lot of work to do in order to make the language usable and commercially viable, or make it ready for being more widely adopted. How do you get a back trace of your program when it crashes? How do we ensure that we run correctly and efficiently on AR 64 when Apple is deploying that architecture more and more? You know, how do we get releases out and be certain that programs that have been written against previously releases will continue to run against the new release? That's something that I really, if this test primops package that uses a quick check style approach to testing the correctness of CMM back end. In JHC, we tend to not use too too many