contract qualifier `performance`
A feature performance that is only true if code needs to be performant might be useful in cases like here: https://github.com/tokiwa-software/fuzion/pull/6050#discussion_r2436448530
Do we want this?
Hmm, what would be the criteria for performance. When would some code be considered reasonably performant and when wouldn't it be?
Hmm, maybe my phrasing is wrong. In some cases (like in the issue mentioned), abstractions can lead to code being worse performance-wise due to use of an abstraction that doesn't always have optimal performance. You could specify a precondition to make sure code only works if the performance is guaranteed to some extent. The extent being developer defined.