Simon Peyton Jones

Thanks! From: Herbert Valerio Riedel [mailto:[email protected]] Sent: 16 November 2016 17:53 To: haskell/haddock [email protected] Subject: Re: [haskell/haddock] Add Markdown support (#244) Relevant further reading: - https://mail.haskell.org/pipermail/haskell-cafe/2013-April/107808.htmlhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.haskell.org%2Fpipermail%2Fhaskell-cafe%2F2013-April%2F107808.html&data=02%7C01%7Csimonpj%40microsoft.com%7Cf0f2858373e44225510e08d40e495b7c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636149155612591232&sdata=Lr%2FHfLXQ3NNk3MqIBbH2eIAyqhkhUlFoCJ%2FNZSZ7keU%3D&reserved=0 - https://mail.haskell.org/pipermail/haskell-cafe/2013-August/110037.htmlhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.haskell.org%2Fpipermail%2Fhaskell-cafe%2F2013-August%2F110037.html&data=02%7C01%7Csimonpj%40microsoft.com%7Cf0f2858373e44225510e08d40e495b7c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636149155612601240&sdata=SJcuqA%2FdGsOJfZ0d6Sx9x5IKbfLBeVF45jBdM7qUk4s%3D&reserved=0 - http://fuuzetsu.co.uk/blog/posts/2013-08-30-why-Markdown-in-Haddock-can't-happen.htmlhttps://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ffuuzetsu.co.uk%2Fblog%2Fposts%2F2013-08-30-why-Markdown-in-Haddock-can%27t-happen.html&data=02%7C01%7Csimonpj%40microsoft.com%7Cf0f2858373e44225510e08d40e495b7c%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636149155612601240&sdata=QSxMK6LMZe9fVaGJR%2B1dppNlV8TwnoBTAzAU2%2F75te8%3D&reserved=0...

Some quick thoughts. First, it's an ambitious project. I rather think there may be other things that need doing first. But perhaps you are motivated by a particular application. Second,...

There are some conclusions from this thread... Adam suggested a workflow, Julian made some additions. It would to collect the agreed process in one place, so we can then follow...

> One option would be to add the process as an addendum to the "Combining Stability with Innovation" proposal. Yes that would be great. We could also add this: https://github.com/simonpj/hf-tech-proposals/blob/ghc-module-naming-2023/proposals/0000-ghc-module-naming.rst...

I would love to have a process agreed here! Thanks @adamgundry for initiating.

It would be helpful to clear up this thread -- see discussion on https://github.com/ghc-proposals/ghc-proposals/pull/625. Especially this comment: https://github.com/ghc-proposals/ghc-proposals/pull/625#issuecomment-1876731498, which suggests that when * Adding deprecation warnings * Adding new exports...

@Bodigrim once the CLC has agreed what it wants, it would be super-helpful to move the three-release policy out of the Haskell Prime wiki, and make it part of the...

> Correct but useless answer: CLC accepted the three-release policy as a guideline in 2015. Aha. Would be possible to modify the CLC's home page to say so, and include...

> But that was the point of the 3-release policy -- to codify things that are usually that obvious and modest Yes that's the point exactly. Whether we say so...

> Now I'm stuck and it seems to me like it is impossible to remove Skip for monadic streams. T We are taking about fusion here, correct? That's only going...