haddock.git - Haddock with an org backend (haddorg).

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fix crash in `haddock-library` on unicode space	Alec Theriault	2020-03-27	1	-7/+7
\| \| \| \| \| \| \| \| \| \| \| \| \|	Our quickcheck tests for `haddock-library` stumbled across an edge case input that was causing Haddock to crash: it was a unicode space character. The root cause of the crash is that we were implicitly assuming that if a space character was not " \t\f\v\r", it would have to be "\n". We fix this by instead defining horizontal space as: any space character that is not '\n'. Fixes #1142
*	Faster 'Text' driven parser combinators	Alec Theriault	2018-11-05	1	-1/+1
\| \| \| \| \| \| \| \|	Perf only change: * use 'getParserState'/'setParserState' to make 'Text'-optimized parser combinators * minimize uses of 'Data.Text.{pack,unpack,cons,snoc}'
*	Replace 'attoparsec' with 'parsec' (#799)	Alec Theriault	2018-04-25	1	-43/+39
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* Remove attoparsec with parsec and start fixing failed parses * Make tests pass * Fix encoding issues The Haddock parser no longer needs to worry about bytestrings. All the internal parsing work in haddock-library happens over 'Text'. * Remove attoparsec vendor * Fix stuff broken in 'attoparsec' -> 'parsec' * hyperlinks * codeblocks * examples Pretty much all issues are due to attoparsec's backtracking failure behaviour vs. parsec's non-backtracking failure behaviour. * Fix small TODOs * Missing quote + Haddocks * Better handle spaces before/after paragraphs * Address review comments
*	Consequently use inClass and notInClass in haddock-library (#617)	Alex Biehl	2017-05-13	1	-3/+6
\| \| \|	These allow attoparsec to do some clever lookup optimization
*	newtype-wrap parser monad	Simon Hengel	2014-11-08	1	-1/+1
\|
*	Add support for markdown links (closes #336)	Simon Hengel	2014-11-03	1	-8/+10
\|
*	Compatibility with older versions of base and bytestring	Simon Hengel	2014-06-18	1	-1/+18
\|
*	Move parser + parser tests out to own package.	Mateusz Kowalczyk	2014-05-05	1	-0/+61
	We move some types out that are necessary as well and then re-export and specialise them in the core Haddock. Reason for moving out spec tests is that if we're working on the parser, we can simply work on that and we can ignore the rest of Haddock. The downside is that it's a little inconvenient if at the end of the day we want to see that everything passes.