On 2014-05-30 19:56, roger peppe wrote:
Both of the above seem like the code would be much more understandable and maintainable if the error kinds were documented and explicitly maintained by the libraries in question. Otherwise you end up with a big risk that you've got all this crufty code written which never gets triggered but isn't obvious that it's cruft.
Oh absolutely! These are situations where you can't control the contract as precisely without stifling change, but there still has to be some kind of contract.
Stifling change is probably the greater evil (for these examples — unlike my category #1) and so a more open-ended contract probably works better here.
Jeroen -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
