Regarding internal class resolving, it seems logical but will slow down
resolution within namespaces. But I doubt this is much of an issue as it
doesn't affect those not using namespaces.
I don't think that makes sense to say "it doesn't affect people not using namespaces" when talking about namespace design.
I believe internal classes should be explicitly disambiguated, even if it looks ugly, so the autoloader can occur at the right place in the chain. Anything else would make namespace+autoload an unusable combination.
Greg, good work on the proposals but I think there's some confusion, even among core devs about the nitty gritty details on some of the proposals. I'd be nice if we can add "allowed / proper" and "not allowed / wrong" examples and such to the RFC-s so it's more obvious what impact each proposal has on code.
As for ::: vs ::, those are virtually not distinguishable in a lot of code, so if that's to go, pick another syntax. ":>" is fine, "\" is fine, ".." is fine.
Regards, Stan Vassilev.