summaryrefslogtreecommitdiff
path: root/testsuite/tests/ffi/should_fail
Commit message (Collapse)AuthorAgeFilesLines
* Testsuite: delete remaining only_compiler_types(['ghc']) setupsThomas Miedema2015-07-141-7/+6
| | | | | No point in pretending other compilers can use the GHC testsuite. This makes the *.T files a bit shorter.
* Improve FFI error reportingSimon Peyton Jones2015-06-023-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 commentsGabor Greif2015-04-101-3/+3
|
* Test Trac #7243Simon Peyton Jones2014-11-273-0/+11
|
* Refactor FFI error messagesSimon Peyton Jones2014-07-258-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 Stolarek2013-09-182-3/+5
|
* Add extra cleaning for ccfail004Ian Lynagh2013-02-161-1/+5
|
* Test Trac #7506Simon Peyton Jones2012-12-193-0/+14
|
* Add testcase for #5664.Paolo Capriotti2012-04-043-0/+39
|
* Add a test for a "value" FFI import with a function typeIan Lynagh2012-02-263-0/+16
|
* Add a test that you can't import "value"s using ccallIan Lynagh2012-02-264-0/+18
| | | | "value"s can only be imported using capi.
* Accept output in ccfail004Ian Lynagh2012-02-211-0/+11
| | | | Newtype handling in FFI decls is no longer relaxed
* accept outputSimon Marlow2011-11-241-11/+0
|
* 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.
* Add a test highlighting a messy case for FFI type errorsIan Lynagh2011-10-013-0/+27
|
* Add a couple more cases to ccfail004Ian Lynagh2011-09-302-4/+20
|
* Add a test for newtypes and the FFIIan Lynagh2011-09-304-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 Terei2011-07-2010-0/+77