Simon Peyton-Jones wrote:
> [...]
> a) to make the worker a NOINLINE thing, so it never got inlined
> anywhere
> b) allow it to be inlined freely in its own module, but then not
> export the inlining of any function that now has an embedded ccall.
It's a little bit hard to decide between a) and b
| I am not sure whether that issues was discussed already, but
| I just noticed that when a module containing foreign import
| declarations is compiled with -O, it may bring some of its
| `__ccall's into the .hi file for inlining purposes.
| The problem is that the `ccall'ed C function
| `gtk_ad
