1424
Golang be like
(i.imgur.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 14 Aug 2023
1424 points (98.0% liked)
Programmer Humor
19551 readers
1024 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
Because you want to know if the first half of the code works at all before you write the whole second half.
Finding all the bits that will be used by the second half and changing the declarations to just expressions is a bunch of extra work. As is adding placeholder code to use the declared variables.
I'm having a hard time envisioning a situation where testing my code requires a bunch of unused variables. Just don't declare the variables until you've started writing the code that uses them...
Most of the time you don't write the code, you change it.
I had tons of situations where I wanted to test deleting a code block which just happened to use an imported library, which the compiler is now complaining about because it's no longer being used.
If that’s the problem, then I would just use something like goimports to auto fix the imports every time I hit save. I never even see those errors so they don’t bother me.