Fix #11 #12
Fix #11 #12
Conversation
To demonstrate that it's now possible to define infix data constructors. Note that infix pattern-matching is not supported yet, so we have to write [(:: x xs) body].
I don't see any code in the prelude in which it would make sense to use
this yet, so I won't demonstrate it there, but here's a small program
demonstrating that it works:
#lang rascal
(data {a && b}
{a & b})
(def mypair : {String && String}
{"foo" & "bar"})
|
I noticed that some infix applications use the infix operator more than once, as in |
|
Neat! Could you add a small test to |
otherwise, the test is useless, because it passes even without the patch
to support infix type constructors: it simply parses {a && b} as
(a && b), a constructor "a" with arguments "&&" and "b".
|
Hmm, why does coveralls still complain? Three times, no less! It looks like the test I added had no effect? |
|
Coveralls is obnoxious and overly loud. I’ve disabled it posting comments on PRs, and I’ve allowed coverage to drop a little bit without being considered a failure. In this case it decreased 0.09%, which is in the noise. I think this looks fine. |
|
Merged in 7add7bc. |
No description provided.