Description
-Xelide-below
is only a single knob. What if I want to elide logging, assertions in my collections library, expensive checks, on different timetables? This is similar to warning output control, where categories associated with code sites can be elevated or suppressed.
Wouldn't it be useful if you could also specify the @elidable level independently for each assertion, because maybe some of them are really computationally expensive and acceptable to remove at runtime, and some of them aren't?
Also, wouldn't it be great if for all these assertions, the code expression is contained in the error message, so that when you don't have access to the source code, it's still possible to understand what went wrong when you input invalid values?
Issue forked from #9838