Excerpts from Johan Tibell's message of 2015-06-04 16:52:30 -0700:
> I guess we should parse it as T a (~b), just as we have unary minus bind
> "tighter" with the following token.
Not in all contexts.
It is true that if you have 'data SLPair a b = SLP a ~ b' you want to
parse 'SLP a (~b)'
But if
On Thu, Jun 4, 2015 at 10:30 PM, Edward Z. Yang wrote:
> Excerpts from Brandon Allbery's message of 2015-06-04 13:06:52 -0700:
> > Looks to me like it's confused about whether a ~ is part of an equality
> > constraint or is a laziness annotation. The former would be illegal at
> that
> > point, t
On 24. 5. 2015 8:43, someone wrote:
> Hi,
Hi. First off, let me note that I proposed multiple things and each affects
this in a different way (and some not at all).
> I saw your email at ghc-devs (I couldnt reply to your email because I wasnt
> subscribed at the time, hence this email) regardin
You need to understand why the shift/reduce conflicts are happening. Happy has
a flag that makes it dump out the state transition tables, and you have to look
at them. there probably is some genuine ambiguity.
Simon
| -Original Message-
| From: ghc-devs [mailto:ghc-devs-boun...@haskel
Excerpts from Brandon Allbery's message of 2015-06-04 13:06:52 -0700:
> Looks to me like it's confused about whether a ~ is part of an equality
> constraint or is a laziness annotation. The former would be illegal at that
> point, though, I'd think? Somewhere it believes a constraint might be
> pos
On Thu, Jun 4, 2015 at 3:52 PM, Adam Sandberg Eriksson <
a...@sandbergericsson.se> wrote:
> However after adding relevant rules for '~' in the parser[2] I get an
> explosion of shift/reduce conflicts as well as 4 extra reduce/reduce
> conflicts, see [3] for the happy info (the states with 36 shift
Hello Adam,
At a guess, ~ is ambiguous with the type equality syntax a ~ b.
You'll probably have to add a new production for types (similar
to atype) which are at the top level of a data constructor definition.
I recently wrote some documentation on how to interpret Happy
info files. There hasn'
Hello *,
I'm working on the -XStrict language extension[1] for this years Google
summer of code. I've started with the smaller -XStrictData (as
documented at the wiki) and have the internals mostly figured out.
However after adding relevant rules for '~' in the parser[2] I get an
explosion of shi
I'm looking for an archive of ghc nightly builds, so I can bisect a suspected
bug at least to a small date range. Does such an archive exist? I have
colleagues who say they used such an archive, and fairly recently, but we can't
seem to find it from the ghc dev wiki today. The date range I a
