| I've added a section on parametric levity polymorphism to the wiki.
| Sorry it took so long.
What's the wiki page?
Simon
|
| I might add some thoughts about first-class `!a` being the only
| semantic hole in our current strict data type situation later if I
| remember to do so.
Luke asks
| Also, can you explain why CorePrep does some floating of its own?
I thought that there was a good reason that CorePrep does floating, but
the more I tried to explain it, the less sense the explanation made. So
here's the reasoning. Maybe I'm missing things, or maybe there's an
Hello,
I'm trying to compile some module with GHC API. I'm going to feed GHC with
Core generated by me.
So far is noticed, that function compileCoreToObj ends with an runtime
error on each call. In spide of this function produces some *.o and *.hi
files. However, produced interface file does not
https://ghc.haskell.org/trac/ghc/wiki/UnliftedDataTypes
On Thu, Oct 8, 2015 at 6:02 AM, Simon Peyton Jones
wrote:
> | I've added a section on parametric levity polymorphism to the wiki.
> | Sorry it took so long.
>
> What's the wiki page?
>
> Simon
> |
> | I might add
On Oct 8, 2015, at 6:02 AM, Simon Peyton Jones wrote:
> What's the wiki page?
https://ghc.haskell.org/trac/ghc/wiki/UnliftedDataTypes
___
ghc-devs mailing list
ghc-devs@haskell.org
If we look at the source code for hscCompileCore, it would seem that it
creates a ModGuts with mkModGuts which has an empty mg_exports, which
means that in all cases there will be no exported items. So it's not
very useful! You should file a bug.
We should fix this, but in the mean time, you
Unless something has changed really recently that I've missed, the typed
holes messages are missing some really important information: instance
information for types in scope. When I am trying to fill in a hole, I look
to the "relevant bindings" to show me what pieces I have available to use.