For people keeping score, I created a branch with this already done
the other day:
https://github.com/ghc/ghc/tree/wip/kill-extcore
Again, unless someone speaks up *real* soon, I'm probably going to get
rid of it before the end of the week - so your timeframe is something
like 72 hours to make a peep before it goes away
On Mon, Apr 28, 2014 at 4:09 AM, Simon Peyton Jones
wrote:
> In principle I think it's a pity to lose External Core. It provides an
> interface to GHC that is based on the simplest possibly connector (a text
> file), and allows GHC's front end or back end to be used by other systems
> written in different languages.
>
> However, as you say, it has received no love for many years. I have
> repeatedly sought someone to support and maintain External Core, but no one
> has stepped forward. That doesn't mean that no one is using it! But the
> absence of bug reports, given how much it has bit-rotted, is a strong
> indicator that no one is.
>
> So I'd like hear from our users, but I won't stand in the way of removing it.
>
> Simon
>
>
> | -Original Message-
> | From: Glasgow-haskell-users [mailto:glasgow-haskell-users-
> | boun...@haskell.org] On Behalf Of Austin Seipp
> | Sent: 27 April 2014 14:14
> | To: ghc-d...@haskell.org; glasgow-haskell-users@haskell.org
> | Subject: Removing -fext-core
> |
> | Hello all,
> |
> | Recently I was wondering something: is there any reason to keep -fext-
> | core around? In particular, it's been broken for a while at this point,
> | see GHC bug #5630[1]
> |
> | As far as I'm aware there really aren't any users of it still around
> | these days, at least none working with a modern GHC. And it seems like
> | if people were to need access to Core, they could use a plugin or some
> | such to get direct access to what they want.
> |
> | Simon mentioned removing ExtCore in face of replacing it with IfaceSyn
> | in the compiler. I'm not entirely sure how much work that would be to
> | bring it all up to scratch if people needed it, but maybe it's worth
> | thinking about.
> |
> | One other issue is a notion of semantics which is present in External
> | Core, but we also now have a documented semantics for GHC's core
> | language as well (which has evolved quite a bit), so I don't know how
> | much that matters.
> |
> | So long story short: I don't think anyone is using it, maintaining it,
> | and it seems subsumed by more recent events.
> |
> | Therefore, if nobody objects, I'd vote to remove -fext-core from GHC,
> | unless someone is willing to step up and really maintain it. If you're
> | using it, you should probably speak up soon I'd imagine...
> |
> | [1] https://ghc.haskell.org/trac/ghc/ticket/5630
> |
> | --
> | Regards,
> |
> | Austin Seipp, Haskell Consultant
> | Well-Typed LLP, http://www.well-typed.com/
> | ___
> | Glasgow-haskell-users mailing list
> | Glasgow-haskell-users@haskell.org
> | http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
>
--
Regards,
Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
