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
At the end of an iteration, if a parameter wasn't used, but was in the previous iteration, then there must be impure control flow occuring. It should be quick to check this after an iteration, and throw an exception if it happens
The text was updated successfully, but these errors were encountered:
BenWoodworth
changed the title
Misuse check: parameters that should've been read
Misuse check: parameters that should've been used
Nov 28, 2023
Note that there are cases where it's okay that parameters aren't used. E.g.
parameterize {
val a by parameterOf('a')
val b by parameter {
a // Uses `a`, but this lazy arguments block only runs on the first iteration (a1)listOf("${a}1", "${a}2")
}
}
Because of this, it may be more complex to track, so may not be worth implementing
At the end of an iteration, if a parameter wasn't used, but was in the previous iteration, then there must be impure control flow occuring. It should be quick to check this after an iteration, and throw an exception if it happens
The text was updated successfully, but these errors were encountered: