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
Currently the JSON formatting for constraints only supports symbolic identifiers, which are difficult to test programmatically since they are fairly unstable. For the purposes of testing it would be convenient if simple expressions could be passed to identify variables for constraints: e.g. write read_mem(0xdeadbeef) rather than trying to guess its symbolic identifier. This would not need to be a complete expression parser, but would only need to be sufficient to handle some cases in order to facilitate testing.
The text was updated successfully, but these errors were encountered:
Currently the JSON formatting for constraints only supports symbolic identifiers, which are difficult to test programmatically since they are fairly unstable. For the purposes of testing it would be convenient if simple expressions could be passed to identify variables for constraints: e.g. write
read_mem(0xdeadbeef)
rather than trying to guess its symbolic identifier. This would not need to be a complete expression parser, but would only need to be sufficient to handle some cases in order to facilitate testing.The text was updated successfully, but these errors were encountered: