Re: Testing that packages still compile

2018-07-03 Thread Sébastien Hinderer
Dear davean and Mikolaj, Many thanks for your responses. I will pass them on to my colleague who may participate to the discussion himself. Best wishes, Sébastien. ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://mail.ha

Re: Testing that packages still compile

2018-05-31 Thread Mikolaj Konarski
You may also be interested in the "Hackage Matrix CI" links on Hackage pages and the non-maintainer updates of packages performed as part of the service to the community. On Thu, May 31, 2018 at 11:32 AM, Sébastien Hinderer wrote: > Dear all, > > I am part of the OCaml development team. As you ma

Re: Testing that packages still compile

2018-05-31 Thread Carter Schonwald
It may be that there’s quite a bit of code that doesn’t have explicit top level type signatures? That’s legal in Haskell but considered bad style / bad practice for packages. I’m not sure if the norms in O’Caml reflect the same inclination. This may complicate localizing type errors On Thu, May

Re: Testing that packages still compile

2018-05-31 Thread davean
My experience may not be representative, but I've done waves of updating packages for a new major GHC release a few times now. I believe for the AMP-containing update of GHC I submitted patches to over 40 packages. My experience is far from universal, but I extensive enough to be informative. In m

Testing that packages still compile

2018-05-31 Thread Sébastien Hinderer
Dear all, I am part of the OCaml development team. As you may know, OCaml has a package manager a bit similar to cabal whose name is opam. One of my colleagues spends quite a lot of time trying to make sure that packages still compile with a new version of the compiler, when we release it. When a