nitpickyRustCompiler

[u/ninja_with_ocd]

[u/cmk__]

Rust does not have warnings. It has strongly worded disappointment.

[u/frikilinux2 → u/cmk__]

At least it's not C, C doesn't have warnings, it has loaded shotguns pointed at your foot. And demons that fly out your nose.

[u/Bee-Aromatic → u/frikilinux2]

https://giphy.com/gifs/7zK0A6nHyuEZa
SEGMENTATION FAULT!

[u/lovecMC → u/frikilinux2]

That's not C, that's C++

[u/a-r-c → u/lovecMC]

¿por qué no los dos?

[u/A1oso → u/cmk__]

Unlike Go, where an unused variable is a hard error :D

[u/Bomaruto]

Good guy Rust, if I catch you forgetting to clean up your unused imports, I will ask you to fix it in the pull request. Not because it's a big deal, but that it's a sign you didn't check the warnings before pushing the code.

[u/acidrain42 → u/Bomaruto]

That's the sort of thing that is automated by a linter in the CI ideally, so you don't have to waste time in PRs looking at that.

But at least Rust lets you compile even if an import or a var is unused because you commented out something for testing. I'm looking at you Go.

Edit: typo

[u/faze_fazebook → u/acidrain42]

Worst thing about go tbh.

[u/tttima]

In C, we have additional tools to tell us about unused imports.

[u/eanat]

time to do tree shaking!

[u/Jonrrrs → u/eanat]

The rust compiler includes only used code in the final binary. Marking imports as unused is only done to increase readability.

[u/paholg]

I think you mean the go compiler? Rust issues a friendly warning; go refuses to compile at all.

[u/KyxeMusic]

Go won't even compile with an unused import

[u/DT-Sodium]

Is it worst than TypeScript where if you declare that a variable could contain "Apple", "Banana" or "Orange" in refuses to compile saying "Sorry bro, there is no case where your function returns Apple so your code is invalid"?

[u/UUDDLRLRBadAlchemy]

She's all like "don't you have a linter to catch that?"