You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The specification currently states that use declarations bring a name into a scope, but that's not exactly true, as imports are not available prior to the use declaration.
namespaceA {
class C {}
}
namespaceB {
// Same scope, 'A\C' should be available right?!$c = newC();
useA\C;
}
Without this restriction, an engine could theoretically make an initial pass to import names from all use declarations, and therefore prevent a name resolution error from occurring.
18-namespaces.md
A namespace-use-declaration imports — that is, makes available — one or more names into a scope, optionally giving them each an alias.
The text was updated successfully, but these errors were encountered:
The specification currently states that use declarations bring a name into a scope, but that's not exactly true, as imports are not available prior to the use declaration.
Without this restriction, an engine could theoretically make an initial pass to import names from all use declarations, and therefore prevent a name resolution error from occurring.
18-namespaces.md
The text was updated successfully, but these errors were encountered: