Add assertion functionality for pre/post conditions. about bouncer HOT 4 CLOSED

Obviously that's not quite right... it would need to be a macro to disappear on compilation, but that's the general idea. I'd be happy to work on it if this functionality is desirable.

Also, do we still need to return a list for each key? The short-circuiting means only one error is returned for each key.

from bouncer.

And now I think this is probably a bad idea. Assertion methods should return nil (as this does), but then it is not suitable for use in a pre/post conditions. This would just be a utility method to stick in code during debugging, but then the needs are just as easily met by (assert (or (valid? args) (pr-str args)). I'm interested in feedback.

from bouncer.

Sorry about the delay. I'll have a think about this and come back to you.

Regarding returning lists, that's there for backwards compatibility - the short-circuiting mechanism hasn't always been there.

from bouncer.

Hi @ToBeReplaced ,

I think this feature should probably be left out of the core functionality and into the user code.

It seems to be mostly concerned with control flow and error presentation. For that reason, I'm closing this issues.

Feel free to re-open it if you think you have better arguments as to why this should be in the core lib.

Thanks

from bouncer.