Re: Scaling back CI (for now)?

2019-02-02 Thread Sebastian Graf
Hi, Am Sa., 2. Feb. 2019 um 16:09 Uhr schrieb Matthew Pickering < matthewtpicker...@gmail.com>: > > All the other flavours should be run once the commit reaches master. > > Thoughts? > That's even better than my idea of only running them as nightlies. In favor! > Cheers, > > Matt > ___

Scaling back CI (for now)?

2019-02-02 Thread Matthew Pickering
Hi all, Everyone has probably noticed that getting anything merged is a real effort at the moment. The main problem is that CI takes in the region of 5-7 hours and then spuriously fails at the end. After 5-7 hours you have to rebase and run CI again and so on. Therefore I propose to run just these

Re: Constructor wrappers vs workers in generated Core

2019-02-02 Thread Christopher Done
On Sat, 2 Feb 2019 at 14:50, Matthew Pickering wrote: > There is no way to turn off wrappers and I don't think it would be > possible to implement easily if at all. Fair enough. > However, they will all probably be inlined after the optimiser runs > but it seems that you don't want to run the op

Re: Constructor wrappers vs workers in generated Core

2019-02-02 Thread Matthew Pickering
There is no way to turn off wrappers and I don't think it would be possible to implement easily if at all. However, they will all probably be inlined after the optimiser runs but it seems that you don't want to run the optimiser at all on the generated core? Perhaps it would be possible to set th

Constructor wrappers vs workers in generated Core

2019-02-02 Thread Christopher Done
Hi all, I'm compiling Haskell modules with this simple function. I'd like to interpret the Core for practical use and also educational use. compile :: GHC.GhcMonad m => GHC.ModSummary -> m GHC.ModGuts compile modSummary = do parsedModule <- GHC.parseModule modSummary typecheckedModul