Previously the syntax was guard ..., true|false, but because we're about to have some long lines, the true|false part was so far away from guard that I misread which is which. I've previously thought about using RPython's guard_true / guard_false syntax, but the solution is more obvious and requires an even tinier change: switch the syntax to guard true|false, ....
[Another minor bug fixed here: we previously added a spurious space character after "false", which caused me to have some surprising diffs earlier today.]
Previously the syntax was
guard ..., true|false
, but because we're about to have some long lines, thetrue|false
part was so far away fromguard
that I misread which is which. I've previously thought about using RPython'sguard_true
/guard_false
syntax, but the solution is more obvious and requires an even tinier change: switch the syntax toguard true|false, ...
.[Another minor bug fixed here: we previously added a spurious space character after "false", which caused me to have some surprising diffs earlier today.]