forked from stanford-centaur/pono
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix naming of automatically generated next-state variables (stanford-…
…centaur#349) If a user has state variables called both `x` and `x.next` in their BTOR2 file, Pono currently throws an error, because `TransitionSystem.make_statevar` creates two solver symbols, an identically-named one for the current value of the state variable, and one with `".next"` appended for the next value. This PR changes the suffix to be something that is less likely to clash with actual signals. It is still possible to cause a crash deliberately, but the only way to avoid that would be to make the variable names less readable and using something like an UUID. Changes included in this commit: * Unify TS constructors * Make next-state suffix configurable * Change TS test to exhibit bug * Change default next-state suffix
- Loading branch information
1 parent
92e7cda
commit 96136ce
Showing
3 changed files
with
16 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters