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
When a contract is broken, only the original expression and its source are shown. It would be nice to also show the runtime values of the variables used in the expression, otherwise it's not really easy to debug e.g. loops.
Maybe some concept of "context" (e.g. loop counter) that should be passed alongside would be nice too. That way, contracts could show the circumstances of the failure more precisely.
The text was updated successfully, but these errors were encountered:
When a contract is broken, only the original expression and its source are shown. It would be nice to also show the runtime values of the variables used in the expression, otherwise it's not really easy to debug e.g. loops.
Maybe some concept of "context" (e.g. loop counter) that should be passed alongside would be nice too. That way, contracts could show the circumstances of the failure more precisely.
The text was updated successfully, but these errors were encountered: