Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | Bump haddock-library version | Mateusz Kowalczyk | 2014-08-31 | 1 | -1/+1 | |
| | ||||||
* | Fix forgotten src | Mateusz Kowalczyk | 2014-08-08 | 1 | -1/+1 | |
| | ||||||
* | Update to attoparsec-0.12.1.1 | Mateusz Kowalczyk | 2014-08-08 | 1 | -5/+6 | |
| | | | | There seems to be memory and speed improvement. | |||||
* | Bump haddock-library to 1.1.0 for release | Mateusz Kowalczyk | 2014-06-25 | 1 | -1/+1 | |
| | ||||||
* | Update Travis, bump version | Mateusz Kowalczyk | 2014-06-19 | 1 | -1/+1 | |
| | ||||||
* | Remove doctest dependency | Simon Hengel | 2014-06-18 | 1 | -8/+0 | |
| | | | | (so that we can use haddock-library with doctest) | |||||
* | Use doctest to check examples in documentation | Simon Hengel | 2014-06-18 | 1 | -0/+8 | |
| | ||||||
* | Comment improvements + few words in cabal file | Mateusz Kowalczyk | 2014-06-18 | 1 | -2/+4 | |
| | ||||||
* | haddock-library: Use -Wall for specs | Simon Hengel | 2014-06-18 | 1 | -0/+2 | |
| | ||||||
* | haddock-library: Do not depend on haddock-library in test suite | Simon Hengel | 2014-06-18 | 1 | -2/+0 | |
| | | | | | I think you either add src to hs-source-dirs or the library to build-depends. But doing both does not make sense (AFAICT). | |||||
* | Compatibility with older versions of base and bytestring | Simon Hengel | 2014-06-18 | 1 | -0/+1 | |
| | ||||||
* | Update cabal files | Mateusz Kowalczyk | 2014-06-18 | 1 | -2/+3 | |
| | | | | | Update repository urls, use subdir property for haddock-library and use a separate versioning scheme for haddock-library in preparation for release. | |||||
* | Update issue tracker URL for haddock-library | Mateusz Kowalczyk | 2014-05-14 | 1 | -1/+1 | |
| | ||||||
* | Move parser + parser tests out to own package. | Mateusz Kowalczyk | 2014-05-05 | 1 | -0/+75 | |
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. |