Open dominicmkennedy opened 2 months ago
I think the issue title is slightly off, since it refers to max twice, rather than min and max.
But setting that aside, this is annoying, I agree. But the problem is one of atomicity. Without the following max_tracelength
statement, the first would put the system in a state that violated the invariant max_tracelength >= min_tracelength
. Forge doesn't do lookahead, and there's not at present a way to make atomic changes to multiple options at once. I'm happy to take suggestions, though.
Temporal Forge code:
Error message: