You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Special elements ..., break and break? are useful to have, but they mess up axioms and properties.
E.g.
property("Commutativity of +" ) = forAll { (x: Language, y: Language) => x + y <-> y + x }
This does not hold for x or y being such a special element.
property("Associativity of *") = forAll { (x: Language, y: Language, z: Language) => (x * y) * z <-> x * (y * z) }
This should not hold if x, y or z is ....
Or maybe it should, and is the problem that we need an alternative for the parentheses (Call(...)?), as long as we are sticking to Scala syntax.
BTW x*y*z should be yet another thing.
The text was updated successfully, but these errors were encountered:
Related to #28. Indeed, we need a way to explicitly say where we want to place the parentheses. I am very reluctant to introduce custom parsers as we did in SubScript, since the learning curve increases and the attractiveness for the users decreases as a result.
We could propose to the Dotty team that their parse tree contains the parentheses, if it doesn't already do so. Then a macro could do the work for us, I think.
Special elements
...
,break
andbreak?
are useful to have, but they mess up axioms and properties.E.g.
This does not hold for
x
ory
being such a special element.This should not hold if
x
,y
orz
is...
.Or maybe it should, and is the problem that we need an alternative for the parentheses (
Call(...)
?), as long as we are sticking to Scala syntax.BTW
x*y*z
should be yet another thing.The text was updated successfully, but these errors were encountered: