It's not especially useful. For literate programming you really need the ability to move blocks of code around without the ceremony of function signatures.
It's not especially useful. For literate programming you really need the ability to move blocks of code around without the ceremony of function signatures.
[0] https://wiki.haskell.org/Literate_programming#Haskell_and_li...
[1] https://okmij.org/ftp/Haskell/class-based-dispatch.lhs
[2] https://okmij.org/ftp/Computation/lightweight-guarantees/eli...
I wrote more about this at <https://news.ycombinator.com/item?id=35985835> and <https://john-millikin.com/software/anansi#history>.
Similarly, if I preview such a file on github I get syntax highlighting for the code but I don't get rendering for the markdown.
So I think the advantage of an 'official' way of saying you're using this arrangement would be communicating intent to more-or-less generic tools.
You could probably even do it with Markdown directly, using fenced code blocks as part of your begin/end lines.
I think you'll find that this approach offers very little benefit over either traditional commentary or linear notebook-style inline code blocks.