It appears to be passing now. I did commit a sequence of 3 patches, 2 of
which should have been squashed together (my bad) and the intermediate
builds were broken, but the final state was OK except for a failure in
setnumcapabilities001. I'll try to reproduce that one today.
Cheers
Simon
On 18
On Tue, Oct 18, 2016 at 4:46 PM, Niklas Hambüchen wrote:
> I'll be lazy and answer the simplest question in this thread :)
>
> On 18/10/16 16:32, Simon Marlow wrote:
> > If not, are you willing to recompile GHC and all your libraries?
>
> Yes.
>
I'll add that managing this is
We've encountered a problem in Intero which is that when inspecting types
of expressions and patterns, sometimes it happens that the type, when
pretty printing, yields variables of the same name but which have different
provenance.
Here's a summary of the issue:
Simon Marlow writes:
> It appears to be passing now. I did commit a sequence of 3 patches, 2 of
> which should have been squashed together (my bad) and the intermediate
> builds were broken, but the final state was OK except for a failure in
> setnumcapabilities001. I'll
This sounds like a thing that should be in the GHC API (the tyvar to
provenance lookup).
Alan
On Wed, Oct 19, 2016 at 2:48 PM, Richard Eisenberg
wrote:
> Interesting problem & solution.
>
> Here's a wacky idea, from a position of utter ignorance about your
> environment:
Interesting problem & solution.
Here's a wacky idea, from a position of utter ignorance about your environment:
could you use color? Already, when I saw `b :: a` in the commentary there,
where `b` is in scope as a type variable, it seemed wrong to me.
In any case, I can answer your simpler
I’m afraid I didn’t understand the issue in the link below. It speaks of
“querying the type”, but I’m not sure what that means. A GHCi session perhaps?
Does this relate to the way GHCi displays types?
I’m a bit lost. A from-the-beginning example, showing steps and what the
unexpected