Design of an Assertable refactoring of postcondition #15
Description
The postcondition interface does not give us a clean and easy way to give feedback about what went wrong in a postcondition. Instead you have to use the monitoring function for that - leading to repeated logic. That's a bit of a shame and a good approach to fixing this issue was identified in #11 but unfortunately due to some miscommunication that work has stalled for the moment. Hopefully we can pick that up again and use the good work that's there!
The idea is to use this issue to discuss the design of this refactoring here in a neutral manner that doesn't result in endless nit-picking of a PR.