Hi all,
The GHC developers are very happy to announce the availability of the
second alpha release in the 9.2.1 series. Binary distributions, source
distributions, and documentation are available at
https://downloads.haskell.org/ghc/9.2.1-alpha2
GHC 9.2 will bring a number of exciting
Ah, yes... I can never remember which is reify and which is reflect. I'm fine
either way. Maybe reifyDict is better.
S
| -Original Message-
| From: Krzysztof Gogolewski
| Sent: 22 April 2021 20:18
| To: Spiwack, Arnaud
| Cc: Simon Peyton Jones ; GHC developers
| Subject: Re:
Happy to see progress being made here. I think Ryan and others have spoken
to any issues I would otherwise raise with the implementation itself.
Currently I find myself reaching for unsafeCoerce over magicDict in most
situations, and I'd really like to be able to stop doing that!
I'm +1 on the
How about 'reifyDict'? The reflection library uses 'reify' to create a
dictionary and 'reflect' to extract a value out of it.
https://hackage.haskell.org/package/reflection-2.1.6/docs/Data-Reflection.html#v:reify
On Thu, Apr 22, 2021 at 3:27 PM Spiwack, Arnaud wrote:
>
> Let me upvote
Let me upvote `reflectDict`.
On Thu, Apr 22, 2021 at 12:41 PM Simon Peyton Jones via ghc-devs <
ghc-devs@haskell.org> wrote:
> Ed, and other ghc-devs
>
> We are busy tidying up magicDict, and making it much more type-safe: see
>
>- https://gitlab.haskell.org/ghc/ghc/-/issues/16646
>-
Ed, and other ghc-devs
We are busy tidying up magicDict, and making it much more type-safe: see
* https://gitlab.haskell.org/ghc/ghc/-/issues/16646
* https://gitlab.haskell.org/ghc/ghc/-/merge_requests/5573
As part of that change we're think of changing its currently-rather-obscure
name.
