Re: Imminent Removal of Make Build System

As a site note, it's probably worth removing or adding a deprecation note to this repo: https://github.com/ghc/hadrian It's the first search result for me for "ghc hadrian" but it's 4 years behind the code in the GHC GitLab. Tom On Thu, Jun 30, 2022 at 08:46:43AM +0100, Matthew Pickering

Re: Options for targeting Windows XP?

On Fri, Mar 26, 2021 at 04:27:58PM +1100, Clinton Mead wrote: > I guess the other dream of mine is to give GHC a .NET backend. For my > problem it would be the ideal solution, but it looks like other attempts in > this regard (e.g. Eta, GHCJS etc) seem to have difficulty keeping up with > updates

Re: Proposal: Don't read environment files by default

> El 28 mar 2019, a las 3:26 PM, Richard Eisenberg escribió: > [...] > 2. I get pilloried every time I say it, but I vastly prefer global package > databases to local ones. I'll second this in one specific context. v2-build has been amazing at work and in general for project-based

Re: Treatment of unknown pragmas

I think Brandon may have misread your example as "{-# HLINT ... #-}". One problem with "{- HLINT" (although I'm personally not in favor of the special-casing) is that if it's just a Haskell comment then it itself is vulnerable to typos. E.g. if I type "{- HILNT foo -}" (L and I swapped), hlint

Re: Proposal: Professionalizing GHC Development

Overall this is a great proposal; glad we're finally modernizing! Still, it's got a pretty steep price tag - maybe we can offset costs with an I.C.O.? ("GHC Coin"?) > El 1 abr 2018, a las 00:56, Gershom B escribió: > > Fellow Haskellers, > > Recently there has been much

Constraint solver iterations

To build the 'vivid' package (on Hackage) with recent versions of GHC (I believe the problem is with 8.0+, didn't see it before then), I need to compile with -fconstraint-solver-iterations=0. (0 meaning unbounded) However, I noticed today that the GHC docs say "Typically one iteration

Re: Help needed: Restrictions of proc-notation with RebindableSyntax

> El 21 dic 2016, a las 02:36, Simon Peyton Jones via ghc-devs > escribió: > > > > I even wonder (whisper it) about taking it out altogether, when Edward says > “many of the original applications for arrows have been shown to be perfectly > suited to being handled by

Re: Allow top-level shadowing for imported names?

I'm weakly against this proposal. I may compile with -Wall, but I read code by many people who don't. When I'm browsing a file and see e.g. import Network.Socket and then later in the file, I see a reference to "recvFrom", I currently know exactly what function is being called. I don't want to