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
The current batchCancelOrders function is difficult to use because the caller runs the risk of the entire transaction reverting if only a single cancellation fails. This is difficult to prevent because a cancellation may fail for non-deterministic reasons (such as the order being expired). This can be improved by doing a no-op instead of reverting for noncritical errors.
The proposed change would alter the logic of cancelOrder and batchCancelOrders, but would not affect the interface.
Motivation
This will improve the reliability of cancelling batches of specific orders.
Specification
The table below compares how failure scenarios are handled when cancelling an order.
Preamble
Discussion: #35
Summary
The current
batchCancelOrders
function is difficult to use because the caller runs the risk of the entire transaction reverting if only a single cancellation fails. This is difficult to prevent because a cancellation may fail for non-deterministic reasons (such as the order being expired). This can be improved by doing a no-op instead of reverting for noncritical errors.The proposed change would alter the logic of
cancelOrder
andbatchCancelOrders
, but would not affect the interface.Motivation
This will improve the reliability of cancelling batches of specific orders.
Specification
The table below compares how failure scenarios are handled when cancelling an order.
Copyright
Copyright and related rights waived via CC0.
The text was updated successfully, but these errors were encountered: