-
**Describe the feature request**
At the moment, when cabal builds a package, it decides first whether or not it will build it with documentation, and then it builds the entire package (possibly inclu…
-
Might be a `stack` bug... some issue with how `stack` installs ghc, perhaps?
```yaml
# stack.yaml
resolver: nightly-2018-04-28
packages:
- .
- haddock-api
- haddock-library
- haddock-test
e…
-
I would find it very helpful if the hover information could include links to Haddock documentation (if documentation is available).
A common situation when working with an unfamiliar library is nee…
sheaf updated
3 years ago
-
Lifted from:
- https://github.com/haskell/hackage-server/issues/1173
`cabal v1-install` chokes on the `hackage-cli` executable in the linking phase. @gbaz suspects it is because `hackage-cli` defi…
-
- [ ] Separate n2o-chat ( #48 )
- [ ] Test n2o dependency in Travis ( #29 )
- [ ] Haddock the Haskell API ( #31 )
- [ ] Haddock Browser-side HTML injection API ( #24 )
- [ ] Ensure n2o-chat sdist work…
-
```
~ $ stack hoogle Conduit
Run from outside a project, using implicit global project config
Using resolver: nightly-2016-08-06 from implicit global project's config file: /home/simon/.stack/global-p…
-
I would like a "fast" mode for Haddock. Often when I'm writing Haddocks, I just want to quickly build the docs and see how they render, and find out if I've introduced any parse errors (e.g. `--^` on …
-
Hi,
I have a big project 300 modules and `cabal haddock` takes minutes to run, but I am interested in refreshing docs for a single module. I don't see any filter flag which fits the goal.
-
Explicit foralls should only be displayed if they declare type parameters out of order. Haddock correctly displays the full type signature of this function:
```haskell
f :: forall b a. a -> b
```…
-
If there is already a '.hi' file present for a module we are haddock-ing, none of the instances in that module will have any location information.
I initially pointed this out in https://github.com…