Parsing errors with Haddock #281

New Issue

2020-02-13T18:35:13+01:00

dschrempf commented

2020-02-13 18:35:13 +01:00

(Migrated from github.com)

Formatting of Haddock comments in the export list of module headers leads to semantic errors with Haddock. For example, the following code

( DataTypeI       
, DataTypeII(DataConstructor)
  -- * Haddock heading
, name
)

is formatted by Brittany to

( DataTypeI
, DataTypeII
  ( DataConstructor
    -- * Haddock heading
  )
, name
)

which throws a Haddock error of the form

parse error on input ‘-- * Haddock heading’
source  >    |      
source  > 23 |     -- * Haddock heading
source  >    |     ^^^^^^^^^^^^

See also issue #231.

Formatting of Haddock comments in the export list of module headers leads to semantic errors with Haddock. For example, the following code ( DataTypeI , DataTypeII(DataConstructor) -- * Haddock heading , name ) is formatted by Brittany to ( DataTypeI , DataTypeII ( DataConstructor -- * Haddock heading ) , name ) which throws a Haddock error of the form parse error on input ‘-- * Haddock heading’ source > | source > 23 | -- * Haddock heading source > | ^^^^^^^^^^^^ See also issue #231.

tfausak commented

2020-07-21 15:14:23 +02:00

(Migrated from github.com)

I think this is a duplicate of #220.

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: hexagoxel/brittany#281