Matthew Pickering writes:
> Dear devs,
>
Hi Matthew and Dan,
First, thanks for your work on this; it is an impressive effort.
Reconstructing a decade of tickets with broken markup, tricky syntax,
and a strange data model is no easy task. Good work so far!
On the whole I am pleasantly surprised
Ah, it looks like it is because of the pre-processor. This file has CPP
enabled:
{-# LANGUAGE CPP #-}
-harendra
On 8 January 2017 at 03:52, Harendra Kumar wrote:
> Hi devs,
>
> I am making a change in runghc on the ghc master branch. When compiling
> the following code (edited/new code in uti
Hi devs,
I am making a change in runghc on the ghc master branch. When compiling the
following code (edited/new code in utils/runghc):
208 splitGhcNonGhcArgs :: [String] -> IO ([String], [String])
209 splitGhcNonGhcArgs args = do
210let (ghc, other) = break notAFlag args
211when (hasUnesc
Hello everyone!
Currently our Phabricator installation is quite old, based on a commit
from last July. Given that I have a bit of breathing room now between
8.0.2 and 8.2.1, I'd like to take this opportunity to do an upgrade
tomorrow if no one objects. Given that this is the first time I have
atte
Hi A.M.,
It's very possible that the list in DynFlags are accumulated in
reverse order to the flags that were provided. The manual is
just talking about user provided flags.
You may also be interested in
https://downloads.haskell.org/~ghc/master/users-guide/extending_ghc.html#frontend-plugins
E
On 01/06/2017 10:37 PM, Edward Z. Yang wrote:
> Hello A.M.,
>
> In 8.0.1 package databases must be specified in the correct order,
> whereas in 7.10 they could be done in any order. This problem
> was fixed in 8.0.2, give it a try.
Thanks for the tip, Edward. That was it!
Following https://ghc.h