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 <simonpj@microsoft.com> wrote:

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 <ghc-devs-bounces@haskell.org> On Behalf Of Moritz Angermann
Sent: 21 October 2020 10:36
To: Ben Gamari <ben@well-typed.com>
Cc: Edward Yang (ezyang@cs.stanford.edu) <ezyang@cs.stanford.edu>; ghc-devs@haskell.org
Subject: Re: Fat interface files?

 

Just to make sure we are aware of all the ongoing efforts. We've been working on ebedding Core into interface files as well.

 

Cheers,

 Moritz

 

On Wed, Oct 21, 2020 at 12:06 AM Ben Gamari <ben@well-typed.com> 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
restarted (e.g. to be pushed down the bytecode pipeline to evaluate TH
splices).

As I recall this is precisely what you implemented in your "fat
interface file" work. Do you recall what the state of this work was? Do
you have a branch with last-known-good work? Do you recall any tricky
questions that remained outstanding?

Cheers,

- Ben
_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs