AndreasPK

I did try `cabal build -w ../ghc_master/_dwarf/stage1/bin/ghc.exe` above and it didn't work. I just tried it quoting the compiler path `cabal build -w "../ghc_master/_dwarf/stage1/bin/ghc.exe"` and that fails the same way....

It seems to work with the version of cabal I built from source today.

> Actually, Cabal 3.6.3.0 has been released (but not cabal-install 3.6.3.0). I don't remember what the changes were, but I think they were requested by the kind GHC folk. I...

For me closing as is is fine.

I like the name `pop` although I can see how it doesn't sound very haskellish somehow.

I assume it's the document in the foot note which merely raises the question: ``` ## 4. The question of `GHC.Exts` Historically `GHC.Exts` has been the primary entry-point for users...

> @AndreasPK IMO, there is `ghc-experimental`, so you can leave out `GHC.Exts`, and expose new primops in `ghc-experimental`. (I personally am fine depending on `ghc-prim` if I need primops; so...

Thanks everyone for the lively discussion! For something like base I think there is a natural tension between a desire for more features and the desire to avoid breaking changes...

For reference these are the gains I see when enabling `-fworker-wrapper-cbv` for containers when running map-benchmarks. I haven't run any of the other benchmarks: ``` Warning: Unknown/unsupported 'ghc' version detected...

I looked into this with @fendor today and it seems to be some sort of race, as eventually it just started working on his machine.