Overloading based on attributes - is it a good idea?

[Ola Fosheim Grøstad]

On Thursday, 30 May 2019 at 05:24:21 UTC, Manu wrote:
> Right. nothrow is the only one that makes any sense at all to 
> me, I've thought that overloading on nothrow might be useful 
> once or twice. Otherwise... pure; like you say, @nogc;

I wonder if overloading on nothrow could be better done as 
overloading on return value. Either you get "return value or 
exception" or you get "wrapped return value".

What other use case is there?