Re: Building stage1 only

> it's very easy to end up in a state where `make` simply can't build, and only > easy fix is a `make clean` Out of sheer curiosity: in what situations does that happen for you? *If* you are working on a single branch, ie. you're not switching back and forth between master and your feature

Re: Building stage1 only

Hi Ömer, in mk/build.mk, set: * Stage1Only=YES * stage=1 * BuildFlavour=devel1 Then 'cd ghc && make'. Don't run make in the toplevel directory. After building the stage1 compiler, it does still start the process of configuring the libraries for the stage2 compiler, but it shouldn't build them.

Confusing error message when universally quantifying unused type variables

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 In Set theory sentence construction, if the letter is not used then no foul. In Haskell, it is not always so. The following is well-typed and works happily: f :: Eq a => b -> b f b = b However, this does not work: f :: ∀ a. Eq a => b -> b f b = b

Re: Confusing error message when universally quantifying unused type variables

Hi, Am Dienstag, den 20.10.2015, 13:10 +0200 schrieb Alexander Berntsen: > In Set theory sentence construction, if the letter is not used then > no foul. In Haskell, it is not always so. > > The following is well-typed and works happily: > f :: Eq a => b -> b > f b = b > > However, this does

Taking a step back

Friends, I'm taking a step back from day-to-day library work. There are two main reasons I use Haskell: on one hand I find writing Haskell educational and fun. On the other I hope to make it a viable alternative to existing mainstream languages. With recent changes to our core libraries, and the

Re: Confusing error message when universally quantifying unused type variables

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I opened a ticket[0] for the "accepting tv in ctx not mentioned in t"-bug. [0] - -- Alexander alexan...@plaimi.net https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG

Re: is this change in TH error message intentional?

Ömer, can you show us the source of Main.hs? Janek Dnia poniedziałek, 19 października 2015, Ömer Sinan Ağacan napisał: > Hi all, > > I realized this change in TH error messages: > > GHC 7.10.2: > > ➜ th-test ghc --make Main.hs > [1 of 1] Compiling Main ( Main.hs, Main.o ) >

Re: Taking a step back

I look forward to seeing yah around at events, as always! On Tuesday, October 20, 2015, Johan Tibell wrote: > Friends, > > I'm taking a step back from day-to-day library work. > > There are two main reasons I use Haskell: on one hand I find writing > Haskell educational

Re: Show instances for GHC internals

Excerpts from Ömer Sinan Ağacan's message of 2015-10-20 06:37:44 -0700: > Edward, do you remember any examples of such code? The big kahuna is interface loading. Everything TyThing from loadDecls is done (unsafely) lazily. In fact, must be, because TyThings are a mutually recursive structure.

Re: Taking a step back

Johan, Thank you so much for all of your contributions to the community. I confess, there are days when I find myself lost in maintenance hell that I feel a desire to throw in the towel as well. (If Eric Mertens and others hadn't picked up so much of the slack on my own projects I'm afraid I

Re: Taking a step back

Thank you for your contributions to the Haskell community. Your work has done a lot, especially for working Haskell programmers like myself and my coworkers. I'm also grateful that you're willing to continue moving the ball forward with unordered-containers and ekg. You didn't mention it

Re: is this change in TH error message intentional?

Originally I had this file: {-# LANGUAGE TemplateHaskell #-} module Main where import Language.Haskell.TH import Language.Haskell.TH.Syntax -- import LiftLoc main :: IO () main = do let loc :: Loc loc = $(locaton) -- loc = $(locaton >>=

Re: Building stage1 only

> Out of sheer curiosity: in what situations does that happen for you? *If* you > are working on a single branch, ie. you're not switching back and forth > between master and your feature branches, this should not happen (and even if > you switch between branches it should still be safe for most

Re: Show instances for GHC internals

> One difficulty is that many of the core type data types, e.g. TyThing, > are (1) a large mutually recursive graph, and (2) have > unsafeInterleaveIO thunks which would induce IO action. So a naive > Show instance would give infinite output and have lots of side effects. > There are many data

Re: Show instances for GHC internals

> There are more interesting parts of your post, but I can respond to this: It > shouldn't take that much time. Once you have ghc-stage2 built, you should be > able to say `make 2` in the ./ghc subdirectory and get a new binary in a few > seconds. > > Using `make 1` in the ./compiler subdirectory