Comment by avgcorrection

I don’t have sufficient experience to judge whether you are correct or not. But I hope that you are correct!

I think code deserves way more assertions and validations. And (like you alluded to) fine-grained ways to turn them on or off; we shouldn’t shy away from expensive tests that might take hundreds of milliseconds just because they might be non-practical to run everywhere—instead we should have configuration to turn them on or off. And not just simple on/off assertions like in Java but things that can have metadata like “cost”, “priority”, and so on.

And, of course, some things (probably the actual contracts) might be always-on.

There’s a lot of exciting potential!