-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run against all passing tests in PureScript compiler test suite #12
Comments
Everything's set up now to work through the tests fixing anything that comes up. The biggest problem now is not having implemented the FFI of many of the dependencies. This is where fun becomes work and contributions would be very welcomed. |
Useful to plot the dependency graph of a package in order to plan out implementing the C FFI of common packages (at least enough of them to complete #12).
We're starting to look really good. @Lupino do you feel up to doing more? I am thinking of taking a stab at |
I've created a number of issues and an encompassing project. If you want to work on any of the issues please make sure it's not already assigned. |
Yay, we're 239/266 tests passing! A few sigsegvs here (likely stack overflows) and a few sigabrt there (likely failed asserts), a missing implementation for |
We're at 255/266 with @Lupino's work on purescript-arrays. Almost there! :) |
We're at 256/266 as of 993d1fd. What's next: I think the missing FFI tests will fall relatively quickly, but there's some corefn parsing issues which might cause a larger hold up, for example: paulyoung/purescript-corefn#57. |
This is done. |
All of these tests should eventually pass using this backend: https://github.com/purescript/purescript/tree/master/tests/purs/passing.
The directory structure is set up such that every
(NAME).purs
file is a test with additional supporting modules optionally residing in a folder named(NAME)/
in the same directory.The logic for this already exists for the most part: https://github.com/felixSchl/purescript-c/blob/5ccdd0584d856584259096eadd11d316375f476d/test/Main.purs#L49-L57.
it
block)The text was updated successfully, but these errors were encountered: