I've been considering sneaking in the Core into the iface as `mi_rules`
with specially chosen names and activation `NeverActive`. The benefit of
this is that we can hijack the compilation pipeline, but still remain
compatible with versions of GHC going quite a while back.
On 20/10/21 18:03, Morit
I found the branch here:
https://github.com/ezyang/ghc/commit/13615ca4e4bf759f323de22a3d182b06c4050f38
On 20/10/20 12:06, Ben Gamari wrote:
Hi Edward,
While chatting with the ghc-ide folks recently I realized that it would
be useful to be able to preserve Core such that compilation can be
rest
Right, my understanding is that they are not sufficient however, as Michael
layed out here
https://gitlab.haskell.org/ghc/ghc/-/wikis/Core-interface-section#unfoldings
This should be linked together better. We'll improve this.
On Wed, Oct 21, 2020 at 5:56 PM Simon Peyton Jones
wrote:
> Thanks M
Thanks Mortiz
That wiki page is about extensible interface files in general. It says nothing
about specifically putting Core terms into interface files.
For the Core part, since GHC already puts Core into unfoldings, the simple
thing is just to expose all unfoldings, no?
Simon
From: ghc-devs
Just to make sure we are aware of all the ongoing efforts. We've been
working on ebedding Core into interface files as well.
Josh has updated the Wiki page here
https://gitlab.haskell.org/ghc/ghc/-/wikis/Extensible-Interface-Files.
Cheers,
Moritz
On Wed, Oct 21, 2020 at 12:06 AM Ben Gamari wrot
