|
Literate haskell files currently contain two (or more?) types on content, but the current `.lhs` extension doesn't offer tools any insight what the non-haskell content of a file is. This is problem when, for example, using Pandoc to convert literate haskell files into other documents. The goal of this proposal is to give other tools the information they need to figure out what the non-haskell content of a file is. This issue was raised two times on the mailing list ([ https://www.haskell.org/pipermail/glasgow-haskell-users/2014-March/024745.html](https://www.haskell.org/pipermail/glasgow-haskell-users/2014-March/024745.html) and [ https://www.haskell.org/pipermail/glasgow-haskell-users/2014-August/025228.html](https://www.haskell.org/pipermail/glasgow-haskell-users/2014-August/025228.html) respectively) and the corresponding Trac ticket [9789](https://gitlab.haskell.org//ghc/ghc/issues/9789).
|
|
Literate haskell files currently contain two (or more?) types on content, but the current `.lhs` extension doesn't offer tools any insight what the non-haskell content of a file is. This is problem when, for example, using Pandoc to convert literate haskell files into other documents. The goal of this proposal is to give other tools the information they need to figure out what the non-haskell content of a file is. This issue was raised two times on the mailing list ([https://www.haskell.org/pipermail/glasgow-haskell-users/2014-March/024745.html](https://www.haskell.org/pipermail/glasgow-haskell-users/2014-March/024745.html) and [ https://www.haskell.org/pipermail/glasgow-haskell-users/2014-August/025228.html](https://www.haskell.org/pipermail/glasgow-haskell-users/2014-August/025228.html) respectively) and the corresponding Trac ticket [9789](https://gitlab.haskell.org/ghc/ghc/issues/9789).
|