possible nested class/struct alias this bug

[Artur Skawina]

On 09/28/13 17:34, Eberhard wrote:
> I came across this unexpected error in the first example, so I tested similar scenarios, but couldn't make any sense of it.

The symbols are looked up in parent scope first, the implicit
conversion happens later.
I'm not sure what the right order /should/ be; unfortunately making
this situation an error would have compiler perf implications (couldn't
then stop the lookup after the first match).

artur