haddock.git/html-test/src, branch ghc-9.4

Follow hlint suggestion: unused LANGUAGE pragma. (#1504)

2022-07-19T07:32:55+00:00

* Follow hlint suggestion: unused LANGUAGE pragma. * Ignore within modules to pass linting and pass tests.

typos (#1464)

2022-03-16T08:44:27+00:00

html-test: Always set language

2021-02-22T09:39:18+00:00

from ghc-9.2 on, the “default” langauge of GHC is expected to change more wildly. To prepare for that (and unblock https://gitlab.haskell.org/ghc/ghc/-/merge_requests/4853), this sets the language for all the test files to `Haskell2010`. This should insolate this test suite against changes to the default. Cherry-picked from https://github.com/haskell/haddock/pull/1341

Merge remote-tracking branch 'origin/ghc-9.0' into ghc-head

2021-01-13T23:39:25+00:00

Merge remote-tracking branch 'origin/ghc-8.10' into ghc-9.0

2021-01-05T21:14:31+00:00

Display linear/multiplicity arrows correctly (#1238)

2020-12-16T19:03:14+00:00

Previously we were ignoring multiplicity and displayed a %1 -> b as a -> b.

testsuite: Update expected output for simplified subsumption

2020-06-03T21:02:31+00:00

Explicit Specificity Support for Haddock

2020-05-20T20:48:38+00:00

Add support for custom section anchors (#1179)

2020-04-25T22:38:11+00:00

This allows to have stable anchors for groups, even if the set of groups in the documentation is altered. The syntax for setting the anchor of a group is -- * Group name #desiredAnchor# Which will produce an html anchor of the form '#g:desiredAnchor' Co-authored-by: Iñaki García Etxebarria

Fallback to `hiDecl` when `extractDecl` fails

2020-04-21T15:06:45+00:00

Sometimes, the declaration being exported is a subdecl (for instance, a record accessor getting exported at the top-level). For these cases, Haddock has to find a way to produce some synthetic sensible top-level declaration. This is done with `extractDecl`. As is shown by #1067, this is sometimes impossible to do just at a syntactic level (for instance when the subdecl is re-exported). In these cases, the only sensible thing to do is to try to reify a declaration based on a GHC `TyThing` via `hiDecl`.