A while ago, we had to cap store.make.int to stop it from considering variables to which we've already stored values (hence store.make.int.single). This was back when we were targeting herd7, and the restriction is likely no longer necessary since we're now targeting litmus7.
At that point, we didn't have flags, so the idea was that we'd make a separate new action if we wanted a non-store.make.int. However, this might actually be a neat example of a use case for flags: we can make a flag like store.allow-multiple-stores and share it across all of the various store.make actions.
A while ago, we had to cap
store.make.int
to stop it from considering variables to which we've already stored values (hencestore.make.int.single
). This was back when we were targetingherd7
, and the restriction is likely no longer necessary since we're now targetinglitmus7
.At that point, we didn't have flags, so the idea was that we'd make a separate new action if we wanted a non-
store.make.int
. However, this might actually be a neat example of a use case for flags: we can make a flag likestore.allow-multiple-stores
and share it across all of the variousstore.make
actions.