[ghc-steering-committee] #190: Module qualified syntax, recommendation: accept

Simon Peyton Jones simonpj at microsoft.com
Tue Apr 23 11:52:17 UTC 2019

I’m ok with ImportQualifiedPost.


From: ghc-steering-committee <ghc-steering-committee-bounces at haskell.org> On Behalf Of Simon Marlow
Sent: 22 April 2019 22:16
To: Joachim Breitner <mail at joachim-breitner.de>
Cc: ghc-steering-committee <ghc-steering-committee at haskell.org>
Subject: Re: [ghc-steering-committee] #190: Module qualified syntax, recommendation: accept

On Wed, 17 Apr 2019 at 08:00, Joachim Breitner <mail at joachim-breitner.de<mailto:mail at joachim-breitner.de>> wrote:

it looks like we agree on accepting this with a pragma, but need to
decide upon the pragma. We had these options:

 * FlexibleImports
 * QualifiedLast
 * QualifiedImportsPostpositive
 * ImportQualifiedPost

Simon M, as the shepherd, care to make a final recommendation about the
pragma and/or ask the authors to come up with one (and amend the

Sometimes I just want someone else to choose the actual syntax while I scowl slightly and accept it :-)

Ok, would anyone be vigorously against ImportQualifiedPost?

(on "FlexibleImports" I'm not very keen on adding an extension flag that we explicitly intend to mean different things in the future. That's just a way of getting around the extension flag policy. Either we think it's a good idea to have flags for every extension, or we don't. Yes I know we've discussed this in the past and there are grey areas, and we do already change the meaning of extensions sometimes. But pre-allocating a bucket for an unknown set of future extensions seems like a step too far to me.)


Joachim Breitner
  mail at joachim-breitner.de<mailto:mail at joachim-breitner.de>

ghc-steering-committee mailing list
ghc-steering-committee at haskell.org<mailto:ghc-steering-committee at haskell.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-steering-committee/attachments/20190423/74a3ab42/attachment-0001.html>

More information about the ghc-steering-committee mailing list