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
With few exceptions, place code in a namespace. Namespaces should have unique names based on the project name, and possibly its path. Do not use using-directives (e.g., using namespace foo). Do not use inline namespaces. For unnamed namespaces, see Internal Linkage.
This wording gives the impression that the using keyword should never be used. However, that would be in direct conflict with an example given later in the section (using ::foo::Bar;). This comment by @tituswinters provides a possible explanation, suggesting it is just a bit of unusual terminology:
Using directives are of the form "using namespace blah;"
Using declarations are of the form "using myproject::some_symbol;"
I think the wording could be made more clear, for example Do not use <i>using namespace</i> directives, if that is the intended meaning.
The text was updated successfully, but these errors were encountered:
Hey ! Hi @tonyruscoe I made a pull request(#845) on this issue with a branch name "clarifying namespace using" Could you please once review it and provide me with feedback or any improvements that need to be done?
In the Namespaces section:
This wording gives the impression that the
using
keyword should never be used. However, that would be in direct conflict with an example given later in the section (using ::foo::Bar;
). This comment by @tituswinters provides a possible explanation, suggesting it is just a bit of unusual terminology:I think the wording could be made more clear, for example
Do not use <i>using namespace</i> directives
, if that is the intended meaning.The text was updated successfully, but these errors were encountered: