Looked at your Contracts library for Ruby. I was just thinking yesterday about starting a project like this! Some thoughts: - I like that the contracts are rig

Looked at your Contracts library for Ruby. I was just thinking yesterday about starting a project like this! Some thoughts: - I like that the contracts are right there in the code and not in a separate file. - The actual Contract methods only run once upon loading each class, so they don't cause a performance hit. I'd like a way to make them all noops (so they don't add any instrumentation) when running in "production". - My thought is that if you can define pre- and post-conditions as you're doing, then you can cut out a lot of the checks in your tests, so that as long as the tests exercise the code, you can rely on the post-conditions to do quite a bit of the validation. Plus you're validating outputs all over the place constantly, so you'd probably catch edge cases you never even expected. - I'm disappointed that your system seems to offer little more than type checking (unless I'm mistaken). I'd like something that gives me true pre- and post-conditions: basically passing a block of Ruby code for each one, with common idioms abbreviated so I don't need to write a whole block if the conditions are simple. Good luck on the project!