summaryrefslogtreecommitdiff
path: root/testsuite/tests/ffi/should_fail/T3066.stderr
Commit message (Collapse)AuthorAgeFilesLines
* Use GHC2021 as default languageJoachim Breitner2021-03-101-5/+5
|
* Add HsSyn prettyprinter testsAlan Zimmerman2016-12-071-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Summary: Add prettyprinter tests, which take a file, parse it, pretty print it, re-parse the pretty printed version and then compare the original and new ASTs (ignoring locations) Updates haddock submodule to match the AST changes. There are three issues outstanding 1. Extra parens around a context are not reproduced. This will require an AST change and will be done in a separate patch. 2. Currently if an `HsTickPragma` is found, this is not pretty-printed, to prevent noise in the output. I am not sure what the desired behaviour in this case is, so have left it as before. Test Ppr047 is marked as expected fail for this. 3. Apart from in a context, the ParsedSource AST keeps all the parens from the original source. Something is happening in the renamer to remove the parens around visible type application, causing T12530 to fail, as the dumped splice decl is after the renamer. This needs to be fixed by keeping the parens, but I do not know where they are being removed. I have amended the test to pass, by removing the parens in the expected output. Test Plan: ./validate Reviewers: goldfire, mpickering, simonpj, bgamari, austin Reviewed By: simonpj, bgamari Subscribers: simonpj, goldfire, thomie, mpickering Differential Revision: https://phabricator.haskell.org/D2752 GHC Trac Issues: #3384
* Refactor FFI error messagesSimon Peyton Jones2014-07-251-3/+4
| | | | | | | | | | | | | | This patch was provoked by Trac #5610, which I finally got a moment to look at. In the end I added a new data type ErrUtils.Validity, data Validity = IsValid -- Everything is fine | NotValid MsgDoc -- A problem, and some indication of why with some suitable combinators, and used it where appropriate (which touches quite a few modules). The main payoff is that error messages improve for FFI type validation.
* Accept type error message changesIan Lynagh2011-10-011-1/+1
| | | | | | | | I think ideally we should give the info from both the old and new messages; i.e. "You wrote X, which I reduced to Y, which isn't valid". That way if Y is an abstract newtype then it will be clearer why the type wasn't valid. We used to only give X, and now we only give Y. Finding X is now a little messier, especially in cases like ccfail005.
* Move tests from tests/ghc-regress/* to just tests/*David Terei2011-07-201-0/+6