Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Testsuite: delete remaining only_compiler_types(['ghc']) setups | Thomas Miedema | 2015-07-14 | 1 | -7/+6 |
| | | | | | No point in pretending other compilers can use the GHC testsuite. This makes the *.T files a bit shorter. | ||||
* | Improve FFI error reporting | Simon Peyton Jones | 2015-06-02 | 3 | -0/+14 |
| | | | | | I refactored TcType FFI functions to return Validity rather than Bool, which turned out to be an easy way to solve Trac #10461. | ||||
* | Typos in error messages and in comments | Gabor Greif | 2015-04-10 | 1 | -3/+3 |
| | |||||
* | Test Trac #7243 | Simon Peyton Jones | 2014-11-27 | 3 | -0/+11 |
| | |||||
* | Refactor FFI error messages | Simon Peyton Jones | 2014-07-25 | 8 | -23/+43 |
| | | | | | | | | | | | | | | 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. | ||||
* | Follow changes in comparison primops (see #6135) | Jan Stolarek | 2013-09-18 | 2 | -3/+5 |
| | |||||
* | Add extra cleaning for ccfail004 | Ian Lynagh | 2013-02-16 | 1 | -1/+5 |
| | |||||
* | Test Trac #7506 | Simon Peyton Jones | 2012-12-19 | 3 | -0/+14 |
| | |||||
* | Add testcase for #5664. | Paolo Capriotti | 2012-04-04 | 3 | -0/+39 |
| | |||||
* | Add a test for a "value" FFI import with a function type | Ian Lynagh | 2012-02-26 | 3 | -0/+16 |
| | |||||
* | Add a test that you can't import "value"s using ccall | Ian Lynagh | 2012-02-26 | 4 | -0/+18 |
| | | | | "value"s can only be imported using capi. | ||||
* | Accept output in ccfail004 | Ian Lynagh | 2012-02-21 | 1 | -0/+11 |
| | | | | Newtype handling in FFI decls is no longer relaxed | ||||
* | accept output | Simon Marlow | 2011-11-24 | 1 | -11/+0 |
| | |||||
* | Accept type error message changes | Ian Lynagh | 2011-10-01 | 1 | -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. | ||||
* | Add a test highlighting a messy case for FFI type errors | Ian Lynagh | 2011-10-01 | 3 | -0/+27 |
| | |||||
* | Add a couple more cases to ccfail004 | Ian Lynagh | 2011-09-30 | 2 | -4/+20 |
| | |||||
* | Add a test for newtypes and the FFI | Ian Lynagh | 2011-09-30 | 4 | -0/+34 |
| | | | | You can only use newtypes in the FFI if the constructor is visible | ||||
* | Move tests from tests/ghc-regress/* to just tests/* | David Terei | 2011-07-20 | 10 | -0/+77 |