On Wed, Apr 06, 2022 at 10:55:09PM +0100, Simon Peyton Jones wrote:
> I see this
> bash$ git status
> On branch wip/romes/ttg-splices-improvements
> Your branch is up to date with 'origin/wip/romes/ttg-splices-improvements'.
>
> modified libraries/Cabal
> +Subproject commit
Friends
I see this
bash$ git status
On branch wip/romes/ttg-splices-improvements
Your branch is up to date with 'origin/wip/romes/ttg-splices-improvements'.
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in
Hi Matthew,
Depending on whether https://gitlab.haskell.org/ghc/ghc/-/issues/21229 is
deemed a blocker for 9.4 (I'd say it is, but YMMV), we should include
https://gitlab.haskell.org/ghc/ghc/-/merge_requests/7788 in the list.
Perhaps we should make it dependent on whether !7788 is ready to merge
Hi all,
We have now forked the 9.4 branch.
There are a few outstanding patches which have not yet been finished
but which are essential to the release.
* (#21019) Windows Toolchain Updates - Ben
* (#20405) Partial Register Stall - Ben/Andreas
* (!7812) Syntactic Unification - Sam
The target
OK. As I said earlier, the 'OtherCon []' unfoldings are unexpected to me.
But if
- We can't reproduce it without a lot of effort
- It's not important to you any more
then let's just let it lie.
Simon
On Wed, 6 Apr 2022 at 08:51, Erdi, Gergo wrote:
> PUBLIC
>
>
>
> Please see this
PUBLIC
Please see this question in my previous email:
* Unfortunately, I am unable to reproduce this from the command line using
the GHC executable, so before I put in the effort of making a minimal example
of using the GHC API to get this result, I would first like to know if this is
Hi Gergo
If you think GHC has a but, can you open a ticket about this? It's all
getting lost in a maze of emails.
Can you also give precise repro instructions? In an attempt to reproduce,
I have just compiled this module (the code you gave)
{-# OPTIONS_GHC -fexpose-all-unfoldings #-}
module
