On Thursday, 9 August 2018 at 04:10:47 UTC, Nicholas Wilson wrote:
The DIP makes the claim that:
* "[@noreturn] has the awkward result of a function specifying
it has a return type T, but never returns that type". When it
is deliberate (such as annotating a fatal error function) the
is almost exclusively `void` (I know of no examples to the
contrary).
Let's say we need to implement an interface with a int func();
member. We can mark it with @noreturn but we can't use TBottom
return type: we're going to break interface implementation.
Andrea
