-
Notifications
You must be signed in to change notification settings - Fork 47
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
Extract JS specifics from library #61
Comments
Thanks! Would be very cool to have it running on So, I'll try building and running your PRs! |
There is There are two spots that still use
The The I don't know that splitting this library into the plain PS stuff and the JS FFI'd stuff is a good idea either. Seems like purerl should just maintain a fork at that point. So I'm leaning toward:
|
OK, not that much at least. It seems these are so small and few, and they aren't changing much, so may the third alternative be that we add the |
That's definitely an option. I would only feel comfortable doing that if the travis stuff could be integrated as well. I guess that means we'd have to have binaries for purerl ready to go (we should have that anyway). I don't know how much an increase on build times that would make either. Are you okay with the build also doing Erlang stuff? |
@joneshf Agreed, a Travis build would be important. I think if we use a build matrix we could run them in parallel, and keep the time down. It would probably increase the complexity of the build configuration, but I'm all right with that. |
Do you have such a build set up for any other purerl projects? |
I don't, I should try to throw one together though. |
Cool! Ping me if there's anything you need help/feedback on. |
As an update in case someone want's to pick this up, this are all FFI files at the moment in v4.0.0-rc1: https://github.com/purescript-spec/purescript-spec/blob/v4.0.0-rc1/src/Test/Spec/Assertions/String.js |
This library is wonderful. I'd like to start using it with
purerl
. But the problem is, it has dependencies on specifics of JavaScript. There are still a couple of FFI modules here, and there's a dependency onpurescript-js-timers
. Are you interested in making this library able to be used by different backends? I don't want to suggest that you should maintain different backends though. That's kind of a big ask from me.I have some ideas how this could be separated out, but I don't want you to have to maintain multiple libraries or have to jump through hoops to get things working. Assuming you're interested in allowing different backends, do you have any thoughts on how you'd like to make that possible?
The text was updated successfully, but these errors were encountered: