Skip to content
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

capi incompatibilities could cause us issues #8

Open
kozross opened this issue Jan 15, 2022 · 1 comment
Open

capi incompatibilities could cause us issues #8

kozross opened this issue Jan 15, 2022 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@kozross
Copy link
Contributor

kozross commented Jan 15, 2022

Based on this GHC issue here, we may have trouble if we enforce capi everywhere. In fact, I've already run into problems with it. Twice.

While in my linked cases, it's not exactly a problem, as having bindings to those helpers isn't strictly necessary, this may cause us trouble in the future with things we do care about. What should our policy be in this case? I can see two solutions:

  • Use ccall for the problem cases; or
  • Wait for GHC to fix the issue upstream, or even commit some time ourselves to fix it.

The first option is the one I prefer, but I'm not sure if it will be problematic or not. The second option is better ecosystemically-speaking, but will take much longer, and essentially limit us only to those compiler version(s) that will have this fix backported to them.

@Kleidukos - what are your thoughts on this?

@kozross
Copy link
Contributor Author

kozross commented Jan 18, 2022

It appears that an upstream fix may be en-route.

@kozross kozross self-assigned this Jan 18, 2022
@kozross kozross added the bug Something isn't working label Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant