+1 from me for keeping the two separate as well. While GHC may be the obviously prevalent Haskell compiler it is a far from the only one,

And I’d hate to have to look at a proposal for adding an extension to GHC (which would be riddled with GHC specific implementation specifics)

Rather than a clean specification.

Maybe I’m naïve but I also see the Haskell committees as doing more than just copy pasting what’s worked. But also evaluate how it can be done

Better. I can perfectly well see situations where the implementation in GHC ended up being less useful than It should be just because of

Implementation quirks/difficulties in GHC.

Cheers,

Tamar

From: Richard Eisenberg
Sent: Thursday, July 21, 2016 18:26
To: Yuras Shumovich
Cc: ghc-users; Gershom B; GHC developers
Subject: Re: Proposal process status

> On Jul 21, 2016, at 11:29 AM, Yuras Shumovich <shumovichy@gmail.com> wrote:

>

> Unfortunately Haskell *is* implementation-defined language. You can't

> compile any nontrivial package from Hackage using Haskell2010 GHC.

Sadly, I agree with this statement. And I think this is what we're trying to change.

> And

> the same will be true for Haskell2020. We rely on GHC-specific

> extensions everywhere, directly or indirectly. If the goal of the

> Haskell Prime is to change that, then the GHC-specific extensions

> should not be first class citizens in the ecosystem.

My hope is that Haskell2020 will allow us to differentiate between standardized extensions and implementation-defined ones. A key part of this hope is that we'll get enough extensions in the first set to allow a sizeable portion of our ecosystem to used only standardized extensions.

>

> We can continue pretending that Haskell is standard-defined language,

> but it will not help to change the situation.

But writing a new standard that encompasses prevalent usage will help to change the situation. And that's the process I'm hoping to contribute to.

Richard

_______________________________________________

ghc-devs mailing list

ghc-devs@haskell.org

http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs