Skip to content

capi incompatibilities could cause us issues #8

Open
@kozross

Description

@kozross

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?

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions