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
{{ message }}
This repository has been archived by the owner on Jun 5, 2023. It is now read-only.
At the moment, there is no way to directly pass arguments to extractors.
This limits the explosiveness and the workaround isn't neat.
If constant arguments could be passed, extractors would gain significant power.
Current
If you need to pass arguments, currently you need to do something like below.
This is because partial application or applications of givens is not allowed.
givenfield as (String, Int) ="y"->2Foo(1, 2) match {
case f @HasField() => println(s"y is 2, x is ${f.x}")
...
}
If arguments are allowed, the above code could be written as
Foo(1, 2) match {
case f @HasField("y"->2) => println(s"y is 2, x is ${f.x}")
...
}
and
term match {
case l @CxPropably(BUF_CRITERIUM) =>BufRewrite(l, hist)
case l @CxProbably(PROP_CRITERIUM) =>Propagate(l, parents)
...
case l @EqvTo(Id) =>BlackHolecase l @EqvTo(S) =>OptimizedS
...
}
The text was updated successfully, but these errors were encountered:
Description
At the moment, there is no way to directly pass arguments to extractors.
This limits the explosiveness and the workaround isn't neat.
If constant arguments could be passed, extractors would gain significant power.
Current
If you need to pass arguments, currently you need to do something like below.
This is because partial application or applications of givens is not allowed.
and
Proposed
If arguments are allowed, the above code could be written as
and
The text was updated successfully, but these errors were encountered: