Hello Alan,
SPJ and I both think that GhcMake is well overdue for a rewrite.
But it's not altogether obvious what the rewrite should look like.
I've made some remarks here:
https://gist.github.com/ezyang/50004e0f842eec5848acad5cf1c22240
I'm OK with small, incremental changes that make tooling's
Thanks Brandon. But I think Ben was probably right; I need cabal install
cabal-install. Somehow this ought to be easier.
I’ll try that when I next get a chance
SImion
From: Brandon Allbery [mailto:allber...@gmail.com]
Sent: 05 September 2016 17:50
To: Simon Peyton Jones
At the moment the standard way to use the GHC API is something like
_ <- load LoadAllTargets
modSum <- getModSummary mn
p <- parseModule modSum
And likewise if renamed or typechecked ASTs are needed.
But the `load` step
On Mon, Sep 5, 2016 at 12:40 PM, Simon Peyton Jones via ghc-devs <
ghc-devs@haskell.org> wrote:
> bash$ which cabal
>
> /home/simonpj/.cabal/bin/cabal
>
> Maybe I need 1.24. Which claims to be installed. But WHERE is it
> installed?
>
>
Try "type cabal". "which" has a nasty tendency to show you
I’m trying to follow the instructions for
https://ghc.haskell.org/trac/ghc/ticket/12562
But I get
cabal new-build llvm-general
--with-ghc=/home/simonpj/5builds/HEAD-4/inplace/bin/ghc-stage2
cabal: unrecognised command: new-build (try --help)
simonpj@cam-05-unx:~/tmp/llvm-general$
Maybe my
Hello everyone,
As you likely know, over the last few months we have been discussing
options for reforming the process for proposing language and
compiler changes to GHC. After much discussion, we have a process [1]
which, while not perfect, is acceptable to a majority of our contributor
base
