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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Build on 7.4 and 7.8	Alec Theriault	2018-10-16	1	-1/+2
\|
*	Replace 'attoparsec' with 'parsec' (#799)	Alec Theriault	2018-04-25	2	-195/+112
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* 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
*	Remove bang pattern	Alec Theriault	2018-03-02	1	-3/+3
\|
*	Support unicode operators, proper modules	Alec Theriault	2018-03-02	1	-2/+23
\| \| \| \| \| \| \| \|	Unicode operators are a pretty big thing in Haskell, so supporting linking them seems like it outweighs the cost of the extra machinery to force Attoparsec to look for unicode. Fixes #458.
*	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
*	Make parser state a newtype	David Feuer	2016-05-24	1	-1/+1
\| \| \| \| \| \|	Previously, it was `data` wrapping a `Maybe`, which seems a bit silly. Obviously, this can be changed back if anyone wants to add more fields some day.
*	(wip) Add support for @since (closes #26)	Simon Hengel	2014-11-16	1	-6/+27
\|
*	newtype-wrap parser monad	Simon Hengel	2014-11-08	2	-1/+129
\|
*	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.