Re: Building the docs, again

Hello, I was talking about the user manual. I imagine that the situation I was in is quite common---you've just implemented some small feature, and you want to write some documentation about it. While working on the documentation, I want to rebuild the manual quickly, so that I can see what it

Re: Building the docs, again

I spent some time with the docs this summer, and wrote a fair bit of the Hadrian documentation building code. So maybe I can shed some light. The question is which docs do you want to build? The library documentation relies on the haddock executable, which is one of the last targets in the

Re: GHCi recompilation avoidance UI

On Wed, Nov 1, 2017 at 1:46 AM, Simon Peyton Jones via ghc-devs wrote: > I'm lost. > > * What causes the undesired behaviour in GHC 8.2.1? > Is it this? > - GHCi wants to load module B with flags F > - There is a B.o but the flags differ > - So GHCi recompiles

RE: Building the docs, again

> Maybe Hadrian will help here? Hadrian can build documentation in various formats but the current implementation is very coarse-grain: we either build all possible docs or no docs at all. It would be relatively easy to add more fine-grain documentation targets and modes. If someone could

RE: GHCi recompilation avoidance UI

I'm lost. * What causes the undesired behaviour in GHC 8.2.1? Is it this? - GHCi wants to load module B with flags F - There is a B.o but the flags differ - So GHCi recompiles B to bytecode * How does (1) help? * Does (2) propose a new command (:load *M vs :load M)? If so, how

RE: Building the docs, again

It is quite confusing that we can be setting the same variable to different values in different places. It would also be quite helpful if we modified the Makefile to say `documentation build target is disabled` or some such, rather then going ahead and building the whole of GHC, only at the