On Thursday, 15 November 2012 at 17:18:04 UTC, Rob T wrote:
I've been wondering for a couple of years about why overloading stops at the argument sig ...

[SNIP]

--rt

I'd say because overall, you gain *very* little out of it, and it costs you much more complex compiler rules.

Most of all though, I'd say it is a bad idea in and out of itself: If you overload on the return type, you open the floodgates to call ambiguity.

I mean, are there even any real use-cases for overload on return type?

Reply via email to