Re: Plugins: How to determine ghc vs ghci

On 24/11/2015 07:37, Levent Erkok wrote: I'm working on a plugin, and would like to be able to tell if it's GHC or GHCi that's running. I tried: df <- getDynFlags let isGHCi = ghcMode df == CompManager Alas, while that correctly tells apart "ghci" from "ghc -c", it also returns True

RE: [GHC] #11160: New exhaustiveness checker breaks ghcirun004

Simon Peyton Jones writes: > No let’s not revert. But: > > · Please put a list of the tickets (there are several) on the wiki > page (where is the wiki page?) > > o perf/compiler/T783 > > o #11163: perf/compiler/T5642 > > o > > · Let’s have a flag to

Re: [commit: ghc] master: Check: More Clang/CPP wibbles (befc4e4)

Gabor Greif writes: > Hi Ben, > > there are still a bunch left: > Indeed there are many in the RTS but for some reason these have never caused trouble. That being said, I have a patch removing them, as well as a linter to ensure that they don't return in the future. I'm waiting

Re: The GHC 8.0 feature freeze is coming

Oh I don't want to block anything from being merged, if anything I'd like to see it get added and actually use the new intrastructure. Unfortunately it looks like I already need some hook changes to make GHCJSi work reasonably well, without having to copy/paste huge loads of GHC code into GHCJS,

Re: The GHC 8.0 feature freeze is coming

Well, its a feature freeze, not a release, so I imagine bugs can still be fixed as they come up. Alan On Fri, Dec 4, 2015 at 4:04 PM, Luite Stegeman wrote: > Oh I don't want to block anything from being merged, if anything I'd like to > see it get added and actually use the

RE: [GHC] #11160: New exhaustiveness checker breaks ghcirun004

No let’s not revert. But: · Please put a list of the tickets (there are several) on the wiki page (where is the wiki page?) o perf/compiler/T783 o #11163: perf/compiler/T5642 o · Let’s have a flag to skip overlap testing so that there is always a workaround ·

Re: [commit: ghc] master: Check: More Clang/CPP wibbles (befc4e4)

Hi Ben, there are still a bunch left: git grep "ASSERT (" Cheers, Gabor On 12/4/15, g...@git.haskell.org wrote: > Repository : ssh://g...@git.haskell.org/ghc > > On branch : master > Link : >

warnings in stage1

Hi devs, I'm getting pattern-match warnings in my stage1 compiler. I assume that this is due to enhanced pattern-match checking. This is good! But I like to build (even stage1) with -Werror. Is this expected? Is someone working on this? Thanks! Richard

Re: warnings in stage1

For what it's worth, I would get behind a movement to allow warnings in stage1, as long as we keep stage2 warning-free. That is, I could forgo my -Werror during stage1 if we felt that it's just better that way. Richard On Dec 4, 2015, at 4:44 PM, Richard Eisenberg wrote:

Re: Plugins: How to determine ghc vs ghci

Thanks Simon.. I tried the 'hscTarget df == HscInterpreted' check, and it works perfectly well. -Levent. On Fri, Dec 4, 2015 at 12:34 AM, Simon Marlow wrote: > On 24/11/2015 07:37, Levent Erkok wrote: > >> I'm working on a plugin, and would like to be able to tell if it's

Phab out of memory

I just tried to update D808, but the following happened. Any ideas? Thanks, Richard rae:22:44:22 ~/Documents/ghc> arc diff origin/master --update D808 --allow-untracked --head HEAD --trace libphutil loaded from '/Users/rae/local/share/libphutil/src'. arcanist loaded from