Ticket #222 (closed defect: fixed)

Opened 22 months ago

Last modified 4 months ago

Accept any input when parsing documentation

Reported by: SimonHengel Owned by:
Priority: major Milestone:
Version: 2.13.1 Keywords:
Cc:

Description

The parser for documentation should never fail. If something is no valid Haddock syntax, then it can still be parsed as ordinary text.

E.g. the following is currently a parse error:

foo bar
> baz

But we should instead parse it as:

DocParagraph (DocString "foo bar\n> baz\n")

That's the way most Markdown parsers do it.

Change History

Changed 7 months ago by anonymous

  • milestone 2.13.2 deleted

Milestone 2.13.2 deleted

Changed 4 months ago by Fūzetsu

  • status changed from new to closed
  • resolution set to fixed

Didn't see this before, we've done this for 2.14.x.

The only parse failures we should be seeing are from GHC when a comment is attached to something we don't expect.

Note: See TracTickets for help on using tickets.