- EPA: Comments in AnchorOperation
- EPA: Remove EpaEofComment

This prevents `data FUN` from being shown at the top of the Prelude docs. Fixes
\#23920 on GHC.

Matthew Pickering authored 1 year ago and sheaf committed 1 year ago

When a class method was reexported, it's default methods were also
showing up in the generated html page.

The simplest and most non-invasive fix is to not look for the default
method if we are just exporting the class method.. because the backends
are just showing default methods when the whole class is exported.

In general it would be worthwhile to rewrite this bit of code I think as
the logic and what gets included is split over `lookupDocs` and
`availExportDecl` it would be clearer to combine the two. The result of
lookupDocs is always just passed to availExportDecl so it seems simpler
and more obvious to just write the function directly.

Vladislav Zavialov authored 1 year ago and sheaf committed 1 year ago

The old reasoning no longer applies, nowadays those names can be
mentioned in export lists.

For GHC 9.8.

This commit avoids running into an incomplete record update warning
in the Hoogle backend of Haddock.

This was only noticed now, because incomplete record updates were broken
in GHC 9.6. Now that they are fixed, we have to avoid running into them!

Bartłomiej Cieślar authored 1 year ago and Ben Gamari committed 1 year ago

MR !10283 changes the alternatives for WarningTxt pass. This MR reflects those changes in the haddock codebase.

Signed-off-by: Bartłomiej Cieślar <bcieslar2001@gmail.com>

Associated data families were being given their own export DocStructureItems,
which resulted in them being documented separately from their classes in
haddocks. This commit fixes it.

Finley McIlwaine authored 1 year ago and Ben Gamari committed 1 year ago

Due to ghc!10469.

Finley McIlwaine authored 1 year ago and Ben Gamari committed 1 year ago

The NFData SourceText instance is now available in GHC

Handle mod_iface mi_warns now being IfaceWarnings

MR !10283 changes the alternatives for WarningTxt pass. This MR reflects those changes in the haddock codebase.

Signed-off-by: Bartłomiej Cieślar <bcieslar2001@gmail.com>

With hi-haddock as is, there is an awkward silence during the load operation.
This commit makes haddock use the default `batchMsg` Messager for progress
reporting, and makes the default GHC verbosity level 1, so the user can see
what GHC is doing.

hi-haddock for ghc 9.6

This section is a bit of a WIP due to the unstable nature of hi-haddock
and the lack of tooling supporting it, but its a good start.

Vladislav Zavialov authored 2 years ago and Matthew Pickering committed 1 year ago

Consider this type signature:

	kindOf :: forall {k} (a :: k). Proxy a -> Proxy k

Prior to this fix, the LaTeX backend rendered it like this:

	kindOf :: forall k a. Proxy a -> Proxy k

Now we preserve explicit specificity and kind annotations.

Vladislav Zavialov authored 2 years ago and Matthew Pickering committed 1 year ago

Prior to this change, atSign was defined as follows:

	atSign unicode = text (if unicode then "@" else "@")

Yes, this is the same symbol '\64' and not your font playing
tricks on you. Now we define:

	atSign = char '@'

Both the LaTeX and the Xhtml backend are updated accordingly.

Neither of these MRs are ready to land yet which causes issues with
other MRs which are ready to land and need haddock changes.

This section is a bit of a WIP due to the unstable nature of hi-haddock
and the lack of tooling supporting it, but its a good start.

* Add --trace-args flag for tracing arguments received to standard output
* Avoid recompiling due to changes in optimization flags
* Update users guide and changes.md

Link to Data.Tuple instead of GHC.Tuple.Prim