undefined | Better HN

0 pointskstrauser4mo ago0 comments

I think the Rust example’s biggest readability sin is using the full names of things like foo::bar::Baz instead of just Baz, but I get why they did that. When you import a lot of things into a file the latter way, it’s easy to get lost in “was that a foo Baz or a wiz Baz?” Sometimes it’s easier just to use the long names everywhere to be explicit.

If I wanted to tweak the Rust project, I’d feel pretty confident I was calling the right things with the right params.

0 comments

cogman104mo ago

That's a style choice that I think comes from former C++ devs.

Java can potentially have the same problem. But because everyone uses an IDE and because it's rarely really an issue, everyone will simply import `Baz` rather than worry about the Foo::Baz and Bat::Baz collision. It does happen in java code, but I can't stress how infrequently it's actually a problem.

kstrauserOP4mo ago

I don’t think that’s quite right. I haven’t written C++ since the 90s, and I use IDEs (Emacs and Zed), but I still sometimes reach a mental threshold where I look at my screen and see way too many names to have to hold in my mental buffer, then decide to make them more explicit.

cogman104mo ago

IDK what the state of Emac/Zed is in terms of type information (I'm sure it depends on the language in question). For Jetbrains/Eclipse/Netbeans if there's a question about a type you can ctrl+click on the type and immediately pull all information about it.

In java, I rarely pay attention to the `import` section (and I know most devs at my company).

You can look up `using namespace std;` in google and you'll find a lot of articles saying it's a bad practice in C++. Everyone recommends writing the full `std::cout` rather than `cout`.

1 more reply

combyn8tor4mo ago

I just import them with unique names if there is a collision - Wiz_Baz and Foo_Baz

j / k navigate · click thread line to collapse

0 pointskstrauser4mo ago0 comments

If I wanted to tweak the Rust project, I’d feel pretty confident I was calling the right things with the right params.

0 comments

cogman104mo ago

That's a style choice that I think comes from former C++ devs.

kstrauserOP4mo ago

cogman104mo ago

In java, I rarely pay attention to the `import` section (and I know most devs at my company).

You can look up `using namespace std;` in google and you'll find a lot of articles saying it's a bad practice in C++. Everyone recommends writing the full `std::cout` rather than `cout`.

1 more reply

combyn8tor4mo ago

I just import them with unique names if there is a collision - Wiz_Baz and Foo_Baz

j / k navigate · click thread line to collapse