aboutsummaryrefslogtreecommitdiff
path: root/html-test/src
Commit message (Collapse)AuthorAgeFilesLines
* Latex type families (#734)Alec Theriault2018-08-041-0/+21
| | | | | | | | | | | | | | | | | | | | * Support for type families in LaTeX The code is ported over from the XHTML backend. * Refactor XHTML and LaTeX family handling This is mostly a consolidation effort: stripping extra exports, inlining some short definitions, and trying to make the backends match. The LaTeX backend now has preliminary support for data families, although the only the data instance head is printed (not the actual constructors). Both backends also now use "newtype" for newtype data family instances. * Add some tests
* Add some more unicode related tests (#872)Alec Theriault2018-07-201-0/+18
| | | | | | | | | | This has been fixed for sure ever since we switched from attoparsec to parsec. Parts of it may have been working before that, but there was a point where this would have failed (see #191). A regression test never hurt anyone. :) (cherry picked from commit 5ec7715d418bfac0f26aec6039792a99a6e89370)
* Misc tests (#858)Alec Theriault2018-07-203-0/+77
| | | | | | | | | | | | * More tests * spliced types * constructor/pattern argument docs * strictness marks on fields with argument docs * latex test cases need seperate directory * Accept tests
* Refactor handling of parens in types (#874)Alec Theriault2018-07-201-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | * Fix type parenthesization in Hoogle backend Ported the logic in the HTML and LaTeX backends for adding in parens into something top-level in 'GhcUtil'. Calling that from the Hoogle backend fixes #873. * Remove parenthesizing logic from LaTeX and XHTML backends Now, the only times that parenthesis in types are added in any backend is through the explicit 'HsParTy' constructor. Precedence is also represented as its own datatype. * List out cases explicitly vs. catch-all * Fix printing of parens for QuantifiedConstraints The priority of printing 'forall' types was just one too high. Fixes #877. * Accept HTML output for quantified contexts test
* Support unicode operators, proper modulesAlec Theriault2018-03-021-0/+6
| | | | | | | | 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.
* Fix infinite loop when specializing instance heads (#723)Alec Theriault2018-02-011-0/+24
| | | | | | | | | * Fix infinite loop when specializing instance heads The bug can only be triggered from TH, hence why it went un-noticed for so long. * Add test for #679 and #710
* Grid Tables (#718)Oleg Grenrus2018-02-011-0/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add table examples * Add table types and adopt simple parser Simple parser is done by Giovanni Cappellotto (@potomak) in https://github.com/haskell/haddock/pull/577 It seems to support single fine full tables, so far from full RST-grid tables, but it's good start. Table type support row- and colspans, but obviously parser is lacking. Still TODO: - Latex backend. Should we use multirow package https://ctan.org/pkg/multirow?lang=en? - Hoogle backend: ? * Implement grid-tables * Refactor table parser * Add two ill-examples * Update CHANGES.md * Basic documentation for tables * Fix documentation example
* Treat escaped \] better in definition lists (#717)Alexander Biehl2018-02-011-0/+55
| | | This fixes #546.
* Fix #548 by rendering datatype kinds more carefully (#702)Ryan Scott2018-02-011-0/+3
|
* Fix: Generate pattern signatures for constructors exported as patterns (#663)Tim Baumann2017-08-062-1/+33
| | | | | | | | | | | | | | | | | | | | | | | | * Fix pretty-printing of pattern signatures Pattern synonyms can have up to two contexts, both having a different semantic meaning: The first holds the constraints required to perform the matching, the second contains the constraints provided by a successful pattern match. When the first context is empty but the second is not it is necessary to render the first, empty context. * Generate pattern synonym signatures for ctors exported as patterns This fixes #653. * Simplify extractPatternSyn It is not necessary to generate the simplest type signature since it will be simplified when pretty-printed. * Add changelog entries for PR #663 * Fix extractPatternSyn error message
* Fix renaming after instance signature specializing (#660)Moritz Drexl2017-08-051-0/+16
| | | | | | | | | | * rework rename * Add regression test for Bug 613 * update tests * update changelog
* Document record fields when DuplicateRecordFields is enabled (#649)Alex Biehl2017-07-031-0/+25
|
* Make per-argument docs for class methods work again (#648)Alex Biehl2017-06-291-0/+6
| | | | | | * Make per-argument docs for class methods work again * Test case
* Don't include names with empty subordinates in maps (#644)Alex Biehl2017-06-232-0/+10
| | | These are unecessary anyway and just blow up interface size
* Haddock support for bundled pattern synonyms (#627)Christiaan Baaij2017-06-092-0/+120
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Haddock support for bundled pattern synonyms * Add fixities to bundled pattern synonyms * Add bundled pattern synonyms to the synopsis * Store bundled pattern fixities in expItemFixities * Add test for bundled pattern synonyms * Stop threading fixities * Include bundled pattern synonyms for re-exported data types Sadly, fixity information isn't found for re-exported data types * Support for pattern synonyms * Modify tests after #631 * Test some reexport variations * Also lookup bundled pattern synonyms from `InstalledInterface`s * Check isExported for bundled pattern synonyms * Pattern synonym is exported check * Always look for pattern synonyms in the current module Another overlooked cornercase * Account for types named twice in export lists Also introduce a fast function for nubbing on a `Name` and use it throughout the code base. * correct fixities for reexported pattern synonyms * Fuse concatMap and map * Remove obsolete import * Add pattern synonyms to visible exports * Fix test * Remove corner case
* Allow user defined signatures for pattern synonyms (#631)Alex Biehl2017-06-031-0/+5
|
* Improve error messageSergey Vinokurov2017-04-291-1/+1
|
* Fix #280. Parsing of module headerSebastian Meric de Bellefon2016-05-151-0/+11
| | | | The initial newlines were counted as indentation spaces, thus disturbing the parsing of next lines
* Merge remote-tracking branch 'idontgetoutmuch/ghc-head' into ghc-headBen Gamari2015-12-251-0/+14
|\
| * Fix the documentation for haddock itself.Dominic Steinitz2015-12-211-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Change notation and add support for inline math. Allow newlines in display math. Add a command line option for the mathjax url (you might want to use a locally installed version). Rebase tests because of extra url and version change. Respond to (some of the) comments. Fix warnings in InterfaceFile.hs
| * Handle inline math with mathjax.Dominic Steinitz2015-12-211-0/+4
| |
* | OrphanInstances: Accept test outputBen Gamari2015-12-241-1/+2
| |
* | html-test/Operators: Clear up ambiguous typesBen Gamari2015-12-231-1/+5
| | | | | | | | | | | | For reasons that aren't entirely clear a class with ambiguous types was accepted by GHC <8.0. I've added a functional dependency to clear up this ambiguity.
* | Add html-test for orphan instances outputBen Gamari2015-12-203-0/+14
|/
* Add examples with type operators to the instances test case.Łukasz Hanuszczak2015-08-211-0/+6
|
* Add basic tests for associated types in instances test case.Łukasz Hanuszczak2015-08-211-0/+28
|
* Add new data type declaration to instance specialization test case. Łukasz Hanuszczak2015-08-211-0/+7
|
* Fix tab-based indentation in instances test case.Łukasz Hanuszczak2015-08-211-6/+6
|
* Extend instances test case to also test multi-name type signatures.Łukasz Hanuszczak2015-08-211-0/+4
|
* Add some test cases for type renamer.Łukasz Hanuszczak2015-08-211-0/+18
|
* Add basic HTML test case for checking instance specialization.Łukasz Hanuszczak2015-08-211-0/+36
|
* Rename advanced types test case and accept new output.Łukasz Hanuszczak2015-08-061-1/+3
|
* Extend advanced types test case with other examples.Łukasz Hanuszczak2015-08-061-0/+14
|
* Delete trailing whitespaceMateusz Kowalczyk2015-07-071-1/+1
|
* Build executable with '-threaded' (fixes #399)Emanuel Borsboom2015-06-122-0/+23
|
* Add simple test case for arbitrary-depth list nesting.Łukasz Hanuszczak2015-05-271-0/+15
|
* Do not insert anchor for section headings in contents boxwatashi2015-04-261-0/+12
|
* Test for anchor defaultingMateusz Kowalczyk2015-03-273-12/+10
| | | | | | | | | I delete the old tests because it turns out that: * test runner would never put them in scope of each other even with imports so just one would suffice * test runner actually needed some hacking to keep links so in the end we would end up with no anchors making them useless
* support GHC 7.10: no Safe-Inferred, Foldable instancejpmoresmau2015-01-221-0/+1
|
* Allow the parser to spit out meta-infoMateusz Kowalczyk2014-12-101-0/+29
| | | | | | | | | | | | | | | Currently we only use it only for ‘since’ annotations but with these patches it should be fairly simple to add new attributes if we wish to. Closes #26. It seems to work fine but due to 7.10 rush I don't have the chance to do more exhaustive testing right now. The way the meta is output (emphasis at the end of the whole comment) is fairly arbitrary and subject to bikeshedding. Note that this makes test for Bug310 fail due to interface version bump: it can't find the docs for base with this interface version so it fails. There is not much we can do to help this because it tests for ’built-in’ identifier, not something we can provide ourselves.
* Fix re-exports of built-in type familiesMateusz Kowalczyk2014-11-041-0/+4
| | | | Fixes #310
* Experimental support for collapsable headersMateusz Kowalczyk2014-10-291-0/+26
| | | | Closes #335
* Omit unnecessary foralls and fix #315Niklas Haas2014-08-241-1/+22
| | | | This also fixes #86.
* Stop testing #188.Mateusz Kowalczyk2014-08-151-7/+0
| | | | | | Because the change is in GHC 7.9 and we now work against 7.8.3, this test no longer makes sense. We revert it until 7.10 becomes the standard version. If anything, there should be a test for this in GHC itself.
* Fix #313 by doing some list munging.Mateusz Kowalczyk2014-08-151-0/+37
| | | | | | I get rid of the Monoid instance because we weren't satisfying the laws. Convenience of having <> didn't outweigh the shock-factor of having it behave badly.
* Fix anchors. Closes #308.Mateusz Kowalczyk2014-06-252-0/+38
|
* Parse identifiers with ^ and ⋆ in them.Mateusz Kowalczyk2014-04-111-0/+22
| | | | Fixes #298.
* We don't actually want unicode hereMateusz Kowalczyk2014-04-111-1/+0
|
* Update test cases for GHC bug #8945, Haddock #188Mateusz Kowalczyk2014-04-033-9/+37
| | | | | | | The order of signature groups has been corrected upstream. Here we add a test case and update some existing test-cases to reflect this change. We remove grouped signature in test cases that we can (Minimal, BugDeprecated &c) so that the test is as self-contained as possible.
* Crash when exporting record selectors of data family instancesNiklas Haas2014-03-311-0/+37
| | | | | | | | | | | | | | | | | | | This fixes bug #294. This also fixes a related but never-before-mentioned bug about the display of GADT record selectors with non-polymorphic type signatures. Note: Associated data type constructors fail to show up if nothing is exported that they could be attached to. Exporting any of the data types in the instance head, or the class + data family itself, causes them to show up, but in the absence of either of these, exporting just the associated data type with the constructor itself will result in it being hidden. The only scenario I can come up that would involve this kind of situation involved OverlappingInstances, and even then it can be mitigated by just exporting the class itself, so I'm not going to solve it since the logic would most likely be very complicated.