Hi Lyle,
There was a temporary build issue, fetching newest master should fix it.
Krzysztof
On Thu, Jun 1, 2023 at 12:03 AM Lyle Kopnicky wrote:
>>
>> Thanks, Georgi and Sebastian.
>
>
> The instructions at https://github.com/alpmestan/ghc.nix and https://ghc.dev/
> seem a bit outdated, then.
The type argument to LitRubbish should be a fixed RuntimeRep. If it is
not, you can file a bug. I have fixed a related bug in f435d55fe969e7.
Krzysztof
On Thu, Sep 15, 2022 at 1:12 PM Csaba Hruska wrote:
>
> I've investigated a bit more. You are right `typeHasFixedRuntimeRep` works
> fine, the
Note that you can use Typed Template Haskell as a workaround, e.g.
f :: forall r (a :: TYPE r). Code Q (a -> a)
f = [||\x -> x||]
In the future this might be integrated better with the restriction
polymorphism checking:
https://gitlab.haskell.org/ghc/ghc/-/issues/18170
https://gitlab.haskell.org
I would like to propose one more option:
withDict :: dt -> (ct => a) -> a
1. This is less symmetric than '(ct => a) -> dt -> a'
but in existing applications magicDict gets the arguments
in the reverse order.
2. Easier to chain 'withDict d1 (withDict d2 ...)'.
3. The name is similar to 'with
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 `reflectDi
We should not reuse the lambda abstraction syntax for foralls. One is
defining a function, and the other a function type. With Dependent
Haskell, we could have:
type T = forall a -> Maybe a
type R = \a -> Maybe a
Here, T has kind * and (\_ -> Nothing) is a value of type T, while R
has kind * -> *
Hi Kai,
This was changed with linear types.
In Core, the constructor Just has now the linear type forall a. a %1 -> Maybe a.
For backwards compatibility, every occurrence of Just is eta-expanded
to \(@a # m) (x :: a) -> Just @a x, so that it can be used in a
non-linear context.
In the case of [],
Hi,
There is an exceptional number of changes stated for the next release.
* Better pattern matching coverage detection
* New windows IO manager
* Linear types
* Large-scale typechecker changes - Taming the Kind Inference Monster,
simplified subsumption
* Better register allocation, improving run
I confirm. I added this in the description of
https://gitlab.haskell.org/ghc/ghc/issues/16830.
Krzysztof
On Mon, Apr 13, 2020 at 1:00 PM Simon Peyton Jones via ghc-devs <
ghc-devs@haskell.org> wrote:
> Friends
>
> I think HsTick and HsBinTick are added (only) by GHC.HsToCore.Coverage
>
> So I thi
Hi,
You can use git tag --contains to see the list of tags containing a
commit; this goes back to ghc-7.2.
A different option is to checkout the configure.ac file for a given commit;
there'll be a line such as
AC_INIT([The Glorious Glasgow Haskell Compilation System], [6.9], [
glasgow-haskell-b.
The search link goes to
https://gitlab.haskell.org/ghc/ghc/wikis/Core-Representation-of-Typed-Template-Haskell-Quotes
but it should go to
https://gitlab.haskell.org/ghc/ghc/wikis/template-haskell/Core-Representation-of-Typed-Template-Haskell-Quotes
On Fri, Mar 22, 2019 at 11:33 AM Matthew Pickerin
Hi,
Does `git clean -fdx .` in libraries/Cabal help? git clean doesn't go into
submodules.
-Krzysztof
On Mon, Dec 3, 2018 at 6:09 PM My Nguyen wrote:
> Hi all,
>
>
> I've finished quite a big rebase and was trying to rebuild, but it failed
> with:
>
> ghc-cabal: Encountered missing dependencie
Python 3 is a likely culprit (though I couldn't confirm it), so I reverted
it. Does it work now?
On Fri, Oct 3, 2014 at 5:51 PM, Herbert Valerio Riedel
wrote:
> On 2014-10-03 at 17:29:31 +0200, Simon Peyton Jones wrote:
> > Perhaps, yes, it is Python 3. I don't know. Could someone revert to
> >
08d8fec86433917b65a93836d2372a5b5c/ghc
>> >
>> >>---
>> >
>> > commit 5bda0d08d8fec86433917b65a93836d2372a5b5c
>> > Author: Krzysztof Gogolewski
>> > Date: Wed Feb 5 20:40:
That's correct: https://ghc.haskell.org/trac/ghc/ticket/3202
It was documented in the GHCi section of documentation, I added now a
mention in the MR section.
On Wed, Feb 5, 2014 at 8:22 PM, Edward A Kmett wrote:
> Isn't it just the default for ghci?
>
> -Edward
>
> > On Feb 5, 2014, at 12:35 A
I have re-sent the question to glasgow-haskell-users; to avoid duplication,
let's continue the thread there.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
Hello,
I propose to enable -XTypeHoles in GHC by default.
Unlike other -X* flags, holes do not really change meaning of the program,
they only change error messages. Instead of "_x not in scope", we
effectively get "_x not in scope, its expected type is a -> a". You get it
only if you precede the
Hello,
Small bikeshedding: I propose to rename recently added Void# (in GHC.Prim)
to Unit#, and void# to unit#. As far as I understand, this type is the
unboxed equivalent of () (i.e. single-element type) rather than Void (i.e.
empty type). The name Void# might be reserved for a type which has
com
18 matches
Mail list logo