Andreas Abel

> I think what's happening is that the table extension is kicking in, because of the `|`. > I think the current behavior of this extension is to regress and...

Judging from the examples given with https://github.github.com/gfm/#table, and its present implementation on github.com, a table header needs to be followed by a delimiter row, otherwise it is not a table....

> You may be able to work around this by moving the `pipeTableSpec` _after_ `defaultSyntaxSpec`, i.e. > > ```haskell > allTheGfmExtensionsExceptPipeTable defaultSyntaxSpec pipeTableSpec > ``` Thanks for the hint! I...

Ok, I try the workaround then!

The problem with the suggested workaround (`pipeTableSpec` after `defaultSyntaxSpec`) is that tables do not parse anymore: ```haskell {-# LANGUAGE LambdaCase #-} {-# LANGUAGE OverloadedStrings #-} {-# LANGUAGE ScopedTypeVariables #-} import...

Thanks for the further research, @jgm. I now applied your workaround to `hackage-server`: - https://github.com/haskell/hackage-server/pull/1114

@zliu41 wrote: > Since `ghc` versions map 1:1 to `base` versions, will remove bounds on `ghc` in future releases. Are you sure about this? Aren't there two GHCs to consider?...

I think because build failures (e.g., https://github.com/ndmitchell/hlint/runs/4691040973?check_suite_focus=true#step:8:286) happen due to changes in the `ghc` module rather than changes in `base`, it would make more sense to put the relevant bounds...

Identical function defined at http://hackage.haskell.org/package/Agda-2.6.1/docs/Agda-Utils-Function.html#v:applyWhen. Also defines `applyUnless` and monadic variants.

> This library is indeed _very_ on the back burner, as there doesn't appear to be much general interest. This is unfortunately a self-fulfilling prophecy. Customers leave (are forced to...