About type aliases in protocol extensions: is this a bug?

I'm certainly sure this is not a bug, but just something that we have never really diagnosed. There is a similar case in the qualified lookup thread.

In that sense, we should diagnose such cases better and ban them altogether.