Closed proppy closed 1 year ago
a workaround is to convert the config value to a string, ex:
"UNIT": "2.4",
"FP_IO_VEXTEND": "expr::2 * $UNIT",
@jeffdi I think we should leave this open, the proper fix is to have OpenLane handle non string vars.
Wait, huh? That's not... how expr is supposed to work
Let me test
Seems to be fixed as of #1509, can you check please?
Description
Currently if encountering a non-string var in an expression:
variable substitutions will fails with the following error:
Expected Behavior
non-string variables get substituted in expressions.
Environment report
Reproduction material
Relevant log output