I wasn’t baiting.
I prefer fully qualified names. This is also a good practice. In fact, it’s even the same in OCaml!
It can seem long at the beginning but our brains are actually good at filtering noise.
Implicitly opening the entire namespace can be bad because you bring a huge bag of names into scope. And since C++ has function overloading, you can find yourself debugging really weird issues. And since it doesn’t happen always, only occasionally, your brain doesn’t keep this issue in mind.
Locally renaming long namespaces is better but naming is generally hard. You take a long bad name and make it a short even worse name.
In fact, your example is even longer due to extra namespaces. In addition, the reader must now load your new Nantes into context.
When I see std::ranges or std::views, I know it refers only to one thing. I don’t need extra context.