On 7/10/17 12:02 AM, Nicholas Wilson wrote:
So far I count four requirements of a solution:
documentation
optimisation
ability to statically reflect upon
ability to implement
Of the approached listed only out{assert(0);} fails the static
reflection check.
I'm pretty much giving up on arguing in this thread, as it seems people
are really keen to add more bloat to the language in spite of the
obvious bloat-free solution.
But I have to ask, what is the benefit of statically determining that a
function is noreturn? I thought it was just a hint to the compiler that
some optimizations can be done for that call?
-Steve