How adverse would you guys feel about a change to the way asserts are handled
so that they are not recoverable? Asserts could latch on to the first failed
assert and always throw an AssertionError on subsequent assert statements.
Another way would be for subsequent asserts to turn off after the
I'm working with developers that have decided to use asserts every time they
want to throw an exception. I feel that their should be something that
dissuades this behavior in the language design. This could be making asserts
not recoverable, making it so you can't stop assert failures from print
