Re: CMM-to-ASM: Register allocation wierdness

Ccing David Spitzenberg, who has thought about proc-point splitting, which is relevant for reasons that we will see below. Harendra Kumar <harendra.ku...@gmail.com> writes: > On 16 June 2016 at 13:59, Ben Gamari <b...@smart-cactus.org> wrote: >> >> It actually

Re: Optimizing "counting" GADTs

"Edward Z. Yang" writes: snip >> Dictionaries are harder to come by, >> but reflection might be an option. > > If I understand correctly, even if you have a Typeable dictionary you > don't necessarily have a way of constructing the other dictionaries > that are available at that

Re: [ANNOUNCE] Glasgow Haskell Compiler 8.0.1, release candidate 1

George Colpitts writes: > That error is only on the binary distribution, building from source works > fine > Great! Let me know if you find any other issues. Thanks George. Cheers, - Ben signature.asc Description: PGP signature

Re: [ANNOUNCE] Glasgow Haskell Compiler 8.0.1, release candidate 1

George Colpitts writes: > installs fine on mac but cabal install vector fails on primitive, looks to > me like gmp library is not provided > I have built a new OS X binary [1] which should be linked against the in-tree libgmp, fixing this issue (which we've been

Re: [ANNOUNCE] Glasgow Haskell Compiler 8.0.1, release candidate 1

Karel Gardas writes: > Hi, > Hi Karel, In the future do you suppose you could just tar these up and post the tarball? box.com is a bit annoying to download files from. Cheers, - Ben signature.asc Description: PGP signature

Re: [ANNOUNCE] Glasgow Haskell Compiler 8.0.1, release candidate 1

Andrés Sicard-Ramírez writes: > I found a different problem installing vector on Ubuntu precise (12.04LTS): > > $ cabal install vector > ... > Installed primitive-0.6.1.0 > Configuring vector-0.11.0.0... > ... >Data/Vector/Generic/Mutable/Base.hs:18:1: error: >

Re: [ANNOUNCE] Glasgow Haskell Compiler 8.0.1, release candidate 1

Andrés Sicard-Ramírez <a...@eafit.edu.co> writes: > On 13 January 2016 at 10:43, Ben Gamari <b...@well-typed.com> wrote: >> The GHC Team is very pleased to announce the first release candidate of >> the Glasgow Haskell Compiler 8.0.1 release. Source and bina

Re: [ANNOUNCE] Glasgow Haskell Compiler 8.0.1, release candidate 1

George Colpitts writes: > installs fine on mac but cabal install vector fails on primitive, looks to > me like gmp library is not provided > > cabal install vector > Resolving dependencies... > Configuring primitive-0.6.1.0... > Failed to install primitive-0.6.1.0 >

Re: [ANNOUNCE] Glasgow Haskell Compiler 8.0.1, release candidate 1

Carter Schonwald writes: > I think 8.0 requires llvm 3.7 and only supports that version. Are we still > planning to bundle opt and LLC in the final release ? > Possibly. The logistics of this still need to be worked out. Cheers, - Ben signature.asc Description:

Re: [ANNOUNCE] Glasgow Haskell Compiler 8.0.1, release candidate 1

Niklas Hambüchen <m...@nh2.me> writes: > On 13/01/16 16:43, Ben Gamari wrote: >> If you have a ticket that you would like to see addressed that does >> not meet one of these criteria, please bring this to our >> attention. > > I would like to nominate > htt

Re: [ANNOUNCE] Glasgow Haskell Compiler 8.0.1, release candidate 1

George Colpitts writes: > Building from src. > > Shouldn't INSTALL.md mention - j option for make ? > This is pretty standard but it wouldn't hurt to mention it. Cheers, - Ben signature.asc Description: PGP signature ___

Dropping bzip2 release tarballs?

tl;dr do you rely on the .bz2 release tarballs on downloads.haskell.org? If so, let us know! Hello everyone, As you may have noticed, a few releases ago we started producing xz-compressed binary distributions in addition to the usual bzip2 tarballs. While preparing 8.0.1-rc1 it was

Re: [ANNOUNCE] Glasgow Haskell Compiler 8.0.1, release candidate 1

David Macek <david.mace...@gmail.com> writes: > On 13. 1. 2016 16:43, Ben Gamari wrote: >> Also note that we currently cannot offer 32-bit Windows builds due to >> breaking changing in a recent Windows 10 upgrade. We'll work to >> resolve this before the 8.0 rel

[ANNOUNCE] Glasgow Haskell Compiler 8.0.1, release candidate 1

The GHC Team is very pleased to announce the first release candidate of the Glasgow Haskell Compiler 8.0.1 release. Source and binary distributions as well as the newly revised users guide can be found at http://downloads.haskell.org/~ghc/8.0.1-rc1/ This is the first in a series of release

RE: Multiple GHC sessions

Simon Peyton Jones writes: > I don't think the state-hack tail should wag the dog here. The nub of > the problem in practice is the shared linker state isn't it? > I'm not sure; it's not clear to me what would break if the linker were used by more than one session at a

Re: Multiple GHC sessions

Alan & Kim Zimmerman writes: > At the moment there are issues with having multiple GHC API sessions > in a single executable, which boil down to GHC having global > variables. > > A quick grep over the GHC sources shows the following instances > >

Re: [ANNOUNCE] Glasgow Haskell Compiler 8.0.1, release candidate 1

Karel Gardas writes: > Hi, > > I've build two builds for Solaris 11.2: > > i386: https://app.box.com/s/1m75kzunzsz6bqh77py5517t39734446 > amd64: https://app.box.com/s/y583zs1tqduz8lbppt66z1qlxms0vytg > > Both binary distributions support shared libraries and use system

Re: CMM-to-ASM: Register allocation wierdness

Harendra Kumar <harendra.ku...@gmail.com> writes: > On 19 June 2016 at 14:03, Ben Gamari <b...@smart-cactus.org> wrote: > >> >> Indeed it would be great if you could provide the program that produced >> this code. >> >> >> It would be great

Re: Force GC calls out of the straight line execution path

Harendra Kumar writes: > Hi Ömer, > > I just checked and I do not see this behavior in 8.0.1 native code, it is > only seen in 7.10.3. So I guess this got fixed in 8.0. > > How about the llvm generated code? Can we control this behavior for llvm > generated code as

Re: [ANNOUNCE] GHC 8.0.1 release candidate 2

Ben Gamari <b...@well-typed.com> writes: > Hello everyone, > snip > > * Compatibility with earlier Cabal versions should be a bit more > robust. > Unfortunately this characterization was perhaps a bit optimistic. Sadly the errors provided by GHC when used with a

Re: [ANNOUNCE] GHC 8.0.1 release candidate 2

Páli Gábor János <pali.ga...@gmail.com> writes: > Hello there, > > 2016-02-07 19:13 GMT+01:00 Ben Gamari <b...@well-typed.com>: >> The GHC Team is very pleased to announce the second release candidate of >> the Glasgow Haskell Compiler 8.0.1 release. > > Fo

[ANNOUNCE] GHC 8.0.1 release candidate 2

Hello everyone, The GHC Team is very pleased to announce the second release candidate of the Glasgow Haskell Compiler 8.0.1 release. Source and binary distributions as well as the newly revised users guide and Haddock documentation can be found at

Re: problem compiling GHC 8.0.1 release candidate 2 src on Apple

George Colpitts writes: snip > ,("target has GNU nonexec stack","False") > ,("target has .ident directive","True") > ,("target has subsections via symbols","True") > ,("Unregisterised","NO") > ,("LLVM llc command","llc") > ,("LLVM opt command","opt") >

Re: [ANNOUNCE] GHC 8.0.1 release candidate 2

George Colpitts writes: > Good news! I assume there will be a Mac OS binary distribution soon? > There is one currently; "Darwin" is the name of the Mac OS X kernel. Cheers, - Ben signature.asc Description: PGP signature

Re: [ANNOUNCE] GHC 8.0.1 release candidate 2

Ben Gamari <b...@well-typed.com> writes: > George Colpitts <george.colpi...@gmail.com> writes: > >> Good news! I assume there will be a Mac OS binary distribution soon? >> > There is one currently; "Darwin" is the name of the Mac OS X kernel. > H

Re: [ANNOUNCE] GHC 8.0.1 release candidate 2

Joachim Breitner <m...@joachim-breitner.de> writes: > Hi, > > Am Sonntag, den 07.02.2016, 19:13 +0100 schrieb Ben Gamari: >> As always, we look forward to hearing about any issues that you >> encounter with this candidate. Thanks to everyone who has contributed so >

Re: Validation failures

Simon Peyton Jones writes: > I’m getting this on a clean HEAD. Is anyone else? > Simon > > Unexpected stat failures: >perf/compiler T5030 [stat not good enough] (normal) >perf/compiler T9872b [stat not good enough] (normal) >perf/compiler T9872c [stat not

Re: Validation failures

Ben Gamari <b...@smart-cactus.org> writes: > Simon Peyton Jones <simo...@microsoft.com> writes: > >> I’m getting this on a clean HEAD. Is anyone else? >> Simon >> >> Unexpected stat failures: >>perf/compiler T5030 [stat not good enough] (no

Re: New type of ($) operator in GHC 8.0 is problematic

Christopher Allen writes: > My understanding was that the implicitly polymorphic levity, did (->) not > change because it's a type constructor? > > Prelude> :info (->) > data (->) a b -- Defined in ‘GHC.Prim’ > Prelude> :k (->) > (->) :: * -> * -> * > > Basically I'm asking

Re: New type of ($) operator in GHC 8.0 is problematic

Ryan Scott writes: > Hi Chris, > > The change to ($)'s type is indeed intentional. The short answer is > that ($)'s type prior to GHC 8.0 was lying a little bit. If you > defined something like this: > > unwrapInt :: Int -> Int# > unwrapInt (I# i) = i > ...

Re: New type of expressions containing (error ...) includes noisy implicit parameter

Christopher Allen writes: > Prelude> let myList = [1, 2, 3 :: Integer] > Prelude> let myList' = myList ++ undefined > Prelude> :t myList > myList :: [Integer] > Prelude> :t myList' > myList' :: (?callStack::GHC.Stack.Types.CallStack) => [Integer] > ... > This isn't just a

Re: GHC build time graphs

Joachim Breitner writes: > Hi Oleg, > > Am Freitag, den 29.01.2016, 00:22 +0200 schrieb Oleg Grenrus: >> Is the same compiler used to build HEAD and 7.10,1? > > Good call. In fact, no: 7.10.1 is built with 7.6.3, while HEAD is built > with 7.10.3. > > Anthony’s link,

RE: CallStack naming

Simon Peyton Jones writes: > OK. Let's make sure the wiki page and documentation reflects this. > It looks like the Wiki [1] hasn't yet been updated. Let's make sure this happens. Thanks! - Ben [1]

RE: Best practices for merging?

Simon Peyton Jones writes: > I'm no git expert here, but > > * Feature branches typically have lots of intermediate fixups. > We don’t want that sequence in the main history; it's like > watching sausage being made, and many intermediate points may > be broken.

Re: Dropping bzip2 release tarballs?

David Feuer writes: > Does this really strain storage infrastructure? There are only a few > blobs per release. > To me the real motivation here is to simplify the distribution preparation process. Currently I need to worry about producing, signing, hashing, and uploading

Re: Build failing

Phyx writes: > Hi Simon, > > I have made a diff to fix it but it hasn't been reviewed yet > https://phabricator.haskell.org/D1878 Thanks Phyx. I just fired off a validation build locally. I'll merge as soon as it passes. Cheers, - Ben signature.asc Description: PGP

Re: Build failing

Ben Gamari <b...@smart-cactus.org> writes: > Phyx <loneti...@gmail.com> writes: > >> Hi Simon, >> >> I have made a diff to fix it but it hasn't been reviewed yet >> https://phabricator.haskell.org/D1878 > > Thanks Phyx. > > I just fi

Re: [ANNOUNCE] Glasgow Haskell Compiler 8.0.1, release candidate 1

Jens Petersen <juhpeter...@gmail.com> writes: > On 14 January 2016 at 00:43, Ben Gamari <b...@well-typed.com> wrote: >> The GHC Team is very pleased to announce the first release candidate of >> the Glasgow Haskell Compiler 8.0.1 release. > > Thanks! - I spent

Re: Best practices for merging?

Jan Stolarek writes: >> If there are multiple commits then a merge commit can serve to logically >> group them. > The cost of this is non-linear history. But I am still not sure what the > actual benefit is? If the > commits come one after another they are still

Re: GHC 8.0.1 status

Christiaan Baaij writes: > Given that I was working on at least once package ( > https://github.com/goldfirere/singletons/pull/142) which gave panics on > GHC8-rc2, couldn't we get at least an GHC8-rc3 before doing an 8.0.1 > release in 3 weeks? As I said in the

Re: [ANNOUNCE] GHC 8.0.1 release candidate 2

Jens Petersen <juhpeter...@gmail.com> writes: > On 8 February 2016 at 03:13, Ben Gamari <b...@well-typed.com> wrote: >> http://downloads.haskell.org/~ghc/8.0.1-rc2/ > > Thank you for RC2. > I'm happy to help. Sorry about the delayed response Jens; I'm still c

GHC 8.0.1 status

tl;dr. Stabilizing the ghc-8.0 is taking a bit longer than was anticipated. The release schedule is being pushed back a bit. Hello everyone, As you likely know we are currently in the depths of the 8.0 release. In fact, under more ideal circumstances I would probably be cutting another

Re: Improving trac notifications

Matthew Pickering writes: > Herbert now seems to have applied the patch. Hopefully this will improve > the email situation for everyone. > Thanks Herbert and Matt! Cheers, - Ben signature.asc Description: PGP signature

RE: GHC 8.0.1 RC 1 and the -fwarn-monomorphism-restriction option

Simon Peyton Jones writes: > No, if that answers your question, good. > > Ben: is this change in the release notes? > Nope, but it will be shortly! Cheers, - Ben signature.asc Description: PGP signature ___ ghc-devs mailing

RE: GHC 8.0.1 RC 1 and the -fwarn-monomorphism-restriction option

Simon Peyton Jones writes: > No, if that answers your question, good. > > Ben: is this change in the release notes? > This now probably ought to be -Wmonomorphism-restriction instead of -fwarn-monomorphism-restriction, correct? Cheers, - Ben signature.asc Description:

Re: [ANNOUNCE] Shaking up GHC

Andrey Mokhov writes: > Dear GHC developers, > > I am happy to announce that the Shaking up GHC project has finally > reached the first milestone. The goal of the project is to design a > new GHC build system based on Shake that will eventually replace the >

Re: vectorisation code?

Manuel M T Chakravarty writes: > The way I see it, the main cost of keeping DPH around is to handle > breakages such as that with vector. I can’t promise to address those > in a timely manner, which is why I agreed to disable/remove DPH. > > However, as Geoff stepped

Re: Options -Wmissed-specialisations, -Wall-missed-specialisations and -Werror

Andrés Sicard-Ramírez writes: > Dear all, > > In GHC 8 RC 1, the `-Wmissed-specialisations` and > `-Wall-missed-specialisations` options generate a warning instead of > an error when using `-Werror`. Is it the expected behaviour? > I would say this can be considered correct.

RE: [ANNOUNCE] Shaking up GHC

Simon Peyton Jones writes: > Very good. > > As I understand it, it can work side-by-side with the existing build > system, correct? That means we don't need to make an either/or choice, > which is very helpful. > > Every day I do sh validate --fast --no-clean How can I do

Re: dynamic linking and GHC 8.0.1 User's Guide

George Colpitts writes: > I believe that static linking will produce a faster program, at least in > some situations. If so it would be good to mention this in section 8.2 of > the user's guide, *Faster: producing a program that runs quicker, * > > I couldn't find

Re: dynamic linking and GHC 8.0.1 User's Guide

George Colpitts writes: > I believe that static linking will produce a faster program, at least in > some situations. If so it would be good to mention this in section 8.2 of > the user's guide, *Faster: producing a program that runs quicker, * > Indeed it would be a

RE: vectorisation code?

Simon Peyton Jones writes: > Making it part of *every* validate is a big ask because it takes so > long to build. > > But we already have "sh validate --slow", which runs a lot more tests > than --fast. So maybe it could be part of --slow? > > And I do think that we should

Re: [ANNOUNCE] Shaking up GHC

Tuncer Ayaz writes: > On 23 January 2016 at 18:16, Herbert Valerio Riedel wrote: > >> On 2016-01-23 at 17:58:12 +0100, Tuncer Ayaz wrote: >> >> [...] >> >> > My suggestion, and what I'd expect, is to make Shake part of GHC's >> > included lib, just like process or xhtml.

RE: [ANNOUNCE] Shaking up GHC

Andrey Mokhov writes: > Herbert, > >> I think it's already quite convenient. After all, you're expected to >> have a minimum GHC bootstrapping environment anyway. So having the >> tools installed (as already do now, e.g. you need alex, happy, and >> ghc to be able

Re: vectorisation code?

Geoffrey Mainland writes: > I didn't mean to suggest that DPH should be part of every build, just > that it should be part of *some* regular build. > > If we're willing to do that, then I'm certainly willing to get DPH back > up and running. > We discussed this in today's

Re: Proposal: Longer Testing Cycle

"Harry ." writes: > "Glasgow Haskell Compiler 8.0.1, release candidate 1" was recently > announced, with a caveat that "This release candidate in particular is > known to suffer from a few significant issues which are being actively > worked upon ... In the coming weeks

GHC 8.0.1 plans

tl;dr: The march towards 8.0.1 continues. Release candidate 2 will likely be cut late next week. If you have a ticket which you'd like to see addressed but suspect we aren't working on then please say so. Hello again GHC-ers, As you likely know, we are currently in the

Re: GHC 8.0.1 plans

Kim-Ee Yeoh <k...@atamo.com> writes: > On Wed, Jan 27, 2016 at 6:34 PM, Ben Gamari <b...@well-typed.com> wrote: > >> tl;dr: The march towards 8.0.1 continues. Release candidate 2 will likely >>be cut late next week. If you have a ticket which you'd l

Re: quick performance measurements

Richard Eisenberg writes: > Hi devs, > > I have a few ideas for tweaks to improve compiler performance. (For > example, reversing the order of comparisons in a short-circuiting > comparison operation.) I don't have a particular test case with a > profile that tells me where

Reconsidering -Wall and -Wcompat

tl;dr. GHC has a new set of warnings, -Wcompat, intended to give users advance notice of coming library changes. We want to know whether you think this set should be included in -Wall. See the Wiki [4] and voice your opinion via the linked poll. Hello everyone, GHC 8.0.1

Re: New type of ($) operator in GHC 8.0 is problematic

"Boespflug, Mathieu" writes: > Hi Ben, > > thanks for the nice summary. I haven't been following all the details > in the meanderings of this thread, but perhaps someone can chime in > with an answer to this simple question: > > * has it been discussed what type ($) should have in

Re: Reconsidering -Wall and -Wcompat

"Boespflug, Mathieu" writes: > Hi Ben, > > could we enlarge the options a bit? I feel that we're in a false > dichotomy currently. I think the issue isn't so much what warnings you > see from the compiler with common settings, so much as "what warnings > will cause my build to

Re: [ANNOUNCE] GHC 8.0.1 release candidate 2

Sven Panne writes: > I'm a little bit late to the 8.0.1 show, but nevertheless: Motivated by the > current discussion about -Wcompat and friends I decided to take a detailed > look at the warnings in my projects and hit a regression(?): Somehow I'm > unable to suppress the

Re: [ANNOUNCE] GHC 8.0.1 release candidate 2

Sven Panne <svenpa...@gmail.com> writes: > 2016-02-15 20:16 GMT+01:00 Ben Gamari <b...@smart-cactus.org>: > >> Sven Panne <svenpa...@gmail.com> writes: >> The reason for this is that the things missing signatures are pattern >> synonyms, which have thei

Re: [ANNOUNCE] GHC 8.0.1 release candidate 2

Sven Panne writes: > 2016-02-16 0:35 GMT+01:00 Matthew Pickering : > >> I have renamed it to -Wmissing-pat-syn-signatures. >> > > Hmmm, things are still wildly inconsistent: > >* "pat" is spelled "pattern" in other flags. > >* We still

Re: New type of ($) operator in GHC 8.0 is problematic

"Boespflug, Mathieu" writes: >> As far as I know, there is currently know way to >> do this in 7.10. >> >> Given how much backlash there has been to changing the type of ($), ... > > Keep in mind... as we saw with FTP, that in this community it's often > unclear just how large or

Re: [ANNOUNCE] GHC 8.0.1 release candidate 2

Sven Panne writes: > 2016-02-16 10:56 GMT+01:00 Herbert Valerio Riedel : > >> [...] but `sig(nature)s` has a precedent, so using `-sigs` wouldn't >> introduce anything new. >> > > I'm fine with "sigs", my point was only the fact that non-abbreviated words

Re: New type of ($) operator in GHC 8.0 is problematic

n use-cases we shouldn't allow them to add noise to our common combinator types. > There are a couple good proposals for addressing levity polymorphism > leaking into the type. I think the one Ben Gamari had in mind that I > thought would be fine is waiting for a patch. > I believe thi

Installing Cabal for GHC 8.0 release candidates

Hello everyone, Our wonderful Cabal release manager Mikhail Glushenkov has kindly uploaded candidate releases of Cabal and cabal-install for use by GHC 8.0 release candidate users. Now updating to a GHC 8.0-compatible Cabal/cabal-install should be as simple as, cabal install \

Re: Is anything being done to remedy the soul crushing compile times of GHC?

Eric Seidel writes: > On Tue, Feb 16, 2016, at 05:49, Simon Peyton Jones wrote: >> * We discussed it in our weekly GHC Skype chat yesterday. One thing that >> would really help is to make it laughably easy to track >>- Micro: whether my commit made anything significantly

Re: Fwd: Is anything being done to remedy the soul crushing compile times of GHC?

Manuel M T Chakravarty writes: > There is currently an interesting discussion on Reddit on GHC compile > times > > > https://www.reddit.com/r/haskell/comments/45q90s/is_anything_being_done_to_remedy_the_soul/ > > I feel that this is a serious problem; so, it probably

Re: Fwd: Is anything being done to remedy the soul crushing compile times of GHC?

Kosyrev Serge <_deepf...@feelingofgreen.ru> writes: > Ben Gamari <b...@smart-cactus.org> writes: >> It would be great if we could get users to submit their >> computationally-heavy, toy projects. Unfortunately, the best testcases >> for us are those with no

Re: Fwd: Is anything being done to remedy the soul crushing compile times of GHC?

Evan Laforge <qdun...@gmail.com> writes: > On Wed, Feb 17, 2016 at 4:38 AM, Ben Gamari <b...@smart-cactus.org> wrote: >> Multiple modules aren't a problem. It is dependencies on Hackage >> packages that complicate matters. > > I guess the problem is when ghc b

Re: Installing Cabal for GHC 8.0 release candidates

George Colpitts writes: > works for me, on my Mac > Thanks for the confirmation, George! Cheers, - Ben signature.asc Description: PGP signature ___ ghc-devs mailing list ghc-devs@haskell.org

Re: Fwd: Is anything being done to remedy the soul crushing compile times of GHC?

Tuncer Ayaz writes: > On 17 February 2016 at 07:40, Evan Laforge wrote: > >> My impression from the reddit thread is that three things are going >> on: >> >> 1 - cabal has quite a bit of startup overhead >> 2 - ghc takes a long time on certain inputs,

Re: Fwd: Is anything being done to remedy the soul crushing compile times of GHC?

Thomas Tuegel <ttue...@gmail.com> writes: > On Wed, Feb 17, 2016 at 2:58 AM, Ben Gamari <b...@smart-cactus.org> wrote: >> Yes, it would be great if someone could step up to look at Cabal's >> performance. Running `cabal build` on an up-to-date tree of a >> modera

Re: [Haskell-cafe] Language complexity & beginners (Was: New type of ($) operator in GHC 8.0 is problematic)

Takenobu Tani writes: > Hi, > > I understood one more point. (I share here.) > The Prelude library document for ghc 8.0 is already well described for > beginners/newcomers. > > * The ($)'s signature of 8.0.1 is already simple (not include forall ...). > * The Bool's kind

Re: Loading GHC into GHCi (reprise)

Erik de Castro Lopo writes: > Hi all, > > Recently Richard showed us how to load GHC into CHCi which ended up > being documented here: > > https://ghc.haskell.org/trac/ghc/wiki/Debugging/Compiler > > That very useful for some things, but doesn't give you access to >

Re: Loading GHC into GHCi (reprise)

Carter Schonwald writes: > Actually that raises a question: is it possible to set a top level ghci > option file pragma for having a module to fobject code ? That would be nice > for exactly this reason. Fobject code doesn't seem to work as of 7.10, > though it seems

Re: Loading GHC into GHCi (reprise)

Ccing Edward, who may have some insight here. Carter Schonwald writes: > Actually that raises a question: is it possible to set a top level ghci > option file pragma for having a module to fobject code ? That would be nice > for exactly this reason. Fobject code

RE: Fwd: Reducing boilerplate

Simon Peyton Jones writes: > Great. Is there a clearly-articulated design on a wiki page? > The design for the relevant GHC extension is here [1]. Cheers, - Ben [1] https://ghc.haskell.org/trac/ghc/wiki/InstanceTemplates signature.asc Description: PGP signature

Re: VisibleTypeApplication and AllowAmbiguousTypes

Andrew Martin writes: > I'm posting this because Richard said it would be the best place to raise > this issue. I know it's a little bit late in the GHC8 development process, > but I would like to get the idea out there. > > To my knowledge, in GHC8, turning on

Re: necessary to build for all platforms?

Erik de Castro Lopo writes: > Richard Eisenberg wrote: > snip >> If I am, is it reasonable to try to teach the build scripts how to avoid >> doing >> this? > > As someone who cares about PowerPC and some other arches, I agree that this > is a reasonable request on the face

Re: Fwd: Reducing boilerplate

Sylvain Henry writes: > Hi devs, > > I would like to add the support for the following automatic > instance-deriving extension: > Hi Sylvain, I suspect the person most qualified to answer these questions will be Simon who is currently in the middle of paper-writing season.

Re: GHC 8.0.1 release plan

Ben Gamari <b...@well-typed.com> writes: > Hello GHCers, > > After numerous delays, I think we may finally be converging on a > (hopefully final) 8.0.1 release candidate. Thanks to the tireless > efforts of Richard Eisenberg, Simon PJ, and many others almost all of > the

GHC 8.0.1 release plan

Hello GHCers, After numerous delays, I think we may finally be converging on a (hopefully final) 8.0.1 release candidate. Thanks to the tireless efforts of Richard Eisenberg, Simon PJ, and many others almost all of the release blocking tickets [1] have now been resolved. There are a few patches

Re: singletons stuff in GHC.Generics?

Carter Schonwald writes: > Hey All, i just noticed that theres some Singletons code in the > GHC.Generics module thats defined but not exported, whats the context on > that? > It's used strictly internally in instances defined in GHC.Generics. For instance,

directory and GHC 8.0.1

Hi Phil, I noticed that directory has a master-1.2.6 branch with at least one useful looking bug-fix on it. Is this the branch that you would prefer to be included in 8.0.1? Cheers, - Ben signature.asc Description: PGP signature ___ ghc-devs mailing

Re: directory and GHC 8.0.1

r...@rufflewind.com writes: >> I noticed that directory has a master-1.2.6 branch with at least one >> useful looking bug-fix on it. Is this the branch that you would prefer >> to be included in 8.0.1? > > I was being cautious and didn't want to add new things between RCs. As > long as no-one

Re: GHC 8.0.1-rc3 source tarball availability

George Colpitts writes: > My understanding is that the required version of llvm is 3.7. Is it safe to > assume that 3.7.1 is also okay? > Yep, in principle anything from the 3.7 series should work. Now that you mention it, we should probably do a better job of

Re: GHC 8.0.1-rc3 source tarball availability

George Colpitts writes: > This fails for me with the following error; I'm using the latest macOS and > Xcode. > Hmm, this is very odd. Unfortunately due to firewall issues I don't have reliable access to our OS X box, so I was unable to test this particular tarball,

Re: TH changes for ghc 8.0

Erik de Castro Lopo writes: > Christiaan Baaij wrote: > >> mapM conT :: [Name] -> Q [Type] :: [Name] -> Q [Pred] :: [Name] -> CxtQ >> >> Those `Name`s are Class names, which are Type constructors, hence `conT` > > Thanks Christiaan, thats got it for me. I'll update the

Re: GHC 8.0.1-rc3 source tarball availability

George Colpitts writes: > Thanks Ben, none of this is obvious to me :) I just read the doc which > doesn't mention distclean or rebuild ​ which I have never had to do on > earlier source distributions​ > ​ Hi George! Sorry for the poor choice of words, indeed the

GHC 8.0.1-rc3 source tarball availability

tl;dr: If you would like to produce a binary distribution for GHC 8.0.1-rc3 then let us know, grab the source distribution and start building. The binary distributions will be all released one week from today. Hello GHC packagers, Austin and I are happy to announce the

Re: GHC 8.0.1-rc3 source tarball availability

Geoffrey Mainland writes: > Does it take a while for the source tarball to show up? All I see is the > Linux binary distribution. > Oh dear, it seems I moved over the wrong file. Sorry about that, everyone. Moreover, I noticed while looking through the patch review queue

Re: GHC 8.0.1-rc3 source tarball availability

Carter Schonwald writes: > http://git.haskell.org/ghc.git also doesn't seem to list an rc3 tag yet :) > That's correct, I mentioned in the original announcement that I didn't push the tag yet in the in case there are issues. I likely won't push it until we have at

Re: directory and GHC 8.0.1

r...@rufflewind.com writes: >> Would you be able to cut a proper 1.2.6 release in time for the 8.0.1 >> release? > > I should be able to. Any idea what that exact date will be? Well, the release candidate 3 source distribution is going out today; the binary distributions will be available at

Re: Broken haddock in new GHC HEAD build

Conal Elliott writes: > I built GHC HEAD from git yesterday (using GHC 7.10.3 on Mac OS 10.9.5), > and the haddock I got dies with > Thanks for the report, Conal! > bash-3.2$ haddock --version > dyld: Symbol not found: _ghc_GHC_modInfoExportszugo_info >

Re: Benchmarking harnesses for a more modern nofib?

Ryan Newton writes: > FYI, moving discussion off the ghc-devs list to avoid spamming it. Check > out this mailing list if interested: > > https://groups.google.com/forum/#!forum/haskell-benchmark-infrastructure > > So far, we're discussing benchmark harnesses and perf

Re: Support for colors in ghci

Никита Нежевский writes: > Hello > > I'm newcomer in GHC. I'd like to realize native support for colors in ghci > (this feature was described in https://ghc.haskell.org/trac/ghc/ticket/10073 > ). Great! I've been hoping someone would come along to look at this problem.

<    1   2   3   4   5   6   7   8   9   10   >