Re: Overring function and its returned type

["Peter C. Chapin" <pcc482719@gmail.com>]

On 11/16/2012 05:40 AM, Maciej Sobczak wrote:

> The problem is that this single example is very artificial and
> represents some corner case that might actually never materialize in
> any of our projects. There are many more examples that are practical
> and do not hit any corner cases of overload resolution and that could
> be easily handled - and therefore could become an added value in the
> type system.


Yes, good point. I think it's in keeping with C++'s philosophy to allow 
what seems reasonable and, like you said, only complain if a problem 
actually arises. I can see the value of that approach. Yet I wonder if 
it increases the risk of an "unrelated" change breaking an existing code 
base by introducing an ambiguity where none existed before.

Peter