Programmer Humor

and it had better be an integer! it had better be an integer, motherfucker!!

This is why I always write my methods from bottom to top. This way I've always got a return statement and I use my variables before they are even declared.

Yeah I think it's trauma due to C/C++'s awful warning system, where you need a gazillion warnings for all the flaws in the language but because there are a gazillion of them and some are quite noisy and false positives prone, it's extremely common to ignore them. Even worse, even the deadly no-brainer ones (e.g. not returning something from a function that says it will) tend to be off by default, which means it is common to release code that triggers some warnings.

Finally C/C++ doesn't have a good packaging story so you'll pretty much always see warnings from third party code in your compilations, leading you to ignore warnings even more.

Based on that, it's very easy to see why the Go people said "no warnings!". An unused variable should definitely be at least a warning so they have no choice but to make it an error.

I think Rust has proven that it was the wrong decision though. When you have proper packaging support (as Go does), it's trivial to suppress warnings in third party code, and so people don't ignore warnings. Also it's a modern language so you don't need to warn for the mistakes the language made (like case fall through, octal literals) because hopefully you didn't make any (or at least as many).

VSCode with Go language support: removes unused variable on save "Fixed that compilation bug for ya, boss"

And people wonder why I stick to Vim.

near, far

The obvious autocomplete is , wherever you are

I try my best to make my IDEs follow the principal that I should be able to type without looking at the screen, but apparently IDEs are really invested in return accepting completions to the point it's often not configurable even when every other key is.

thank you for flooding my memory with a bunch of silly 90s car commercials

Visual Studio: PROPERTY DOESN'T EXIST ON TYPE!! NOTHING EXISTS ANYMORE!!!!!! REALITY HAS COLLAPSED!

Me: What? I haven't even touched that class, let me check.

Visual Studio: Oops, nevermind, héhé 🙃

Then it automatically imports the library for you too lol

It's probably gonna be optimized out by the compiler. However, linters will mark it for you, since it suggests that you actually wanted to do something with that variable and forgot about it after declaration.

... Or it can be removed to reduce visual noise once it's not necessary anymore after refactoring.

Lets say you use a variable named abcd in your function. And a variable named abcb in a for loop inside the same function. But because reasons you mistakenly use abcd inside that loop and modify the wrong variable, so that your code sometimes doesnt work properly.

It's to prevent mistakes like that.

A similar thing is to use const when the variable is not modified.

Because it's code that literally doesn't do anything. Some languages won't even let you compile without special instructions.

How do you mean? You can't type a word without using it in a word processor. Once the word is typed out it's been used. Variables need to be declared then used so 2 separate steps.