Re: Getting rid of -XImpredicativeTypes

Oops, I completely missed you saying that despite reading your post multiple times and actually quoting it. Sorry about that. But yes, that makes it very clear, thanks. Doable, even if a pain in the neck. The motivation for my question was that I vaguely recalled encountering code that uses

Status of Harbormaster

Hello everyone, Over the last few weeks I have been gradually pushing away at increasing our Harbormaster coverage. I'm happy to report that Harbormaster should now test commits on, * x86_64 Ubuntu Linux * x86_64 Mac OS X Sierra * x86_64 Windows (although the bugs are still being worked out

Re: Allow top-level shadowing for imported names?

By all means make the proposal -- I like this idea. > On Oct 3, 2016, at 4:29 AM, Herbert Valerio Riedel wrote: > > Hi *, > > I seem to recall this was already suggested in the past, but I can't > seem to find it in the archives. For simplicity I'll restate the idea: > >

RE: Allow top-level shadowing for imported names?

Fine with me! Simon | -Original Message- | From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of | Herbert Valerio Riedel | Sent: 03 October 2016 09:29 | To: ghc-devs | Subject: Allow top-level shadowing for imported names? | | Hi *, | | I

Re: Allow top-level shadowing for imported names?

I don't see why not. (But then again I wasn't around for Haskell98!) Edward Excerpts from Herbert Valerio Riedel's message of 2016-10-03 10:29:06 +0200: > Hi *, > > I seem to recall this was already suggested in the past, but I can't > seem to find it in the archives. For simplicity I'll

Allow top-level shadowing for imported names?

Hi *, I seem to recall this was already suggested in the past, but I can't seem to find it in the archives. For simplicity I'll restate the idea: foo :: Int -> Int -> (Int,Int) foo x y = (bar x, bar y) where bar x = x+x results merely in a name-shadowing warning (for