As far as I can tell, these changes aren’t yet in GHC 8.6:

* https://github.com/haskell/haddock/pull/905 
<https://github.com/haskell/haddock/pull/905> is on Haddock’s 8.6 branch, but 
GHC 8.6 hasn’t yet bumped the submodule.
* https://github.com/haskell/haddock/pull/893 
<https://github.com/haskell/haddock/pull/893> is not even yet on Haddock’s 8.6 
branch. Note that this one requires matching GHC-side changes to be 
cherry-picked too.

I think the idea is loosely for GHC 8.6 to ship whatever is in the Haddock 
`ghc-8.6` branch.

> On Aug 23, 2018, at 6:46 AM, Simon Jakobi via ghc-devs <[email protected]> 
> wrote:
> 
> Is the fix in https://github.com/haskell/haddock/issues/837 
> <https://github.com/haskell/haddock/issues/837> included in 8.6.1, too?
> 
> The fix is both on ghc's ghc-8.6 branch and on haddock's ghc-8.6 branch.
> 
> Currently I'm a bit confused about exactly which Haddock release/snapshot 
> will be shipped with 8.6.1...
> 
> I'm not sure either. CC'ing Herbert.
> 
> Am Do., 23. Aug. 2018 um 11:07 Uhr schrieb Sven Panne <[email protected] 
> <mailto:[email protected]>>:
> Am Di., 21. Aug. 2018 um 17:14 Uhr schrieb Simon Jakobi via ghc-devs 
> <[email protected] <mailto:[email protected]>>:
> I talked to Alex about these today:
> 
> * PR #905 has been merged.
> * PR #893 requires the merge of https://phabricator.haskell.org/D5003 
> <https://phabricator.haskell.org/D5003>. Apart from that there were no 
> objections.
> 
> Just another Haddock-related question: Is the fix in 
> https://github.com/haskell/haddock/issues/837 
> <https://github.com/haskell/haddock/issues/837> included in 8.6.1, too? 
> Currently I'm a bit confused about exactly which Haddock release/snapshot 
> will be shipped with 8.6.1...
> _______________________________________________
> ghc-devs mailing list
> [email protected]
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

_______________________________________________
ghc-devs mailing list
[email protected]
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Reply via email to