[Sugawara]

I just started revising C++ for my interviews, my goal is to understand the crux of the language and build a competitive programming practice around it. I came across the namespace controversy which differs from every programmers' style. Some use the namespaces for competitive programming and others prefer the later with building apps in C++.

According to me, a good coding practice should be carried across irrespective of projects.

Would you go with writing

Code

using namespace std

which imports all the objects from the "Standard Template Library" or would rather prefer using it with the scope resolution style?

Code

std::*object*

It would be great if you can provide a justification/reason around this.

[int main()]

https://stackoverflow.com/questions/1452...d-practice

[Sugawara]

https://stackoverflow.com/questions/1452...d-practice

Could have googled it as well.
Wanted to know what people on HF specifically C++ developers go with!

[akali]

I typically don't use the global namespace directive. Rather, just individually declare the namespace along with each type.

Code

using namespace std;//bad

using std::cout; //not great but ok
using std::cin //not great but ok

std::cin << x ;//preferred
std::cout >> x >> std::endl; //preferred

[HFDone]

Could have googled it as well.
Wanted to know what people on HF specifically C++ developers go with!

they google it too https://www.geeksforgeeks.org/using-name...d-practice

[morph]

std::cout > using namespace std;

I almost never use "using namespace" in any context.
Namespaces are used for a reason.

[Goodies]

I typically don't use the global namespace directive. Rather, just individually declare the namespace along with each type.

Code

using namespace std;//bad

using std::cout; //not great but ok
using std::cin //not great but ok

std::cin << x ;//preferred
std::cout >> x >> std::endl; //preferred

This is my answer too. Explicit is better than implicit.

[4Txe4y33C9zvNhMj]

I typically don't use the global namespace directive. Rather, just individually declare the namespace along with each type.

Code

using namespace std;//bad

using std::cout; //not great but ok
using std::cin //not great but ok

std::cin << x ;//preferred
std::cout >> x >> std::endl; //preferred

Exactly this.

[m1n0r1tyrep0rt]

As a general rule, I do not declare using statements.

I explicitly state the identifier I am using. For example, std::cin or std::cout, for the simple reason that in larger development projects (millions of lines of code) I do not want to be debugging redefinitions or other strangeness.

Explicitly stating the namespace of the identifier, while might be few more keystrokes, trust me, its better having exercising those fingers, than losing your temper later in the project. Bitter experience.