I love go

i love go

That's nice, retard.

GO IS GOD

./thread

>unused as errors

>remove a bit of code to test things out

HURR DURR UNUSED VARIABLE

no thank you

My condolences

>unused as errors

That's some full retard shit right there.

Go really marks unused variables as errors?

Yes. I didn't believe it either after reading this...

but I did a search and found the complaints and the retarded reasoning behind it.

Unused variables and imports are the bane of compiling time

Off yourself
Comment it out if you are not using it

This is how large code bases decay

You first, shitlord.

Yes. So? It makes perfect sense.

This is what monGOloids actually believe.

What does an unused variable do to your code? Lmao brain dead retard

There isn't a single answer to that question, brain dead retard.

People write outlines of their program which have unused variables until they go back and flesh everything out. I would understand an unused variable warning but an error? Why should I be prevented from compiling to test out my program?

You'll understand when you write more than bank manager apps for your first year c++ class.

>Readable code is reliable code.
>Rob Pike

I tolerated it long enough to ship a a couple projects. It's good enough I guess, but at the end of the day it's nothing more than PHP for retards so yeah, so long and thanks for all the unchecked {}interface.

Me too.

The rationale is that unused variables are indicative of bugs. I've found this to be the case. I'm not particularly thrilled at it being an error but it's not a great hindrance anyway.

>gophags are desperate to justify their shit language

top kek

>"ship a a [sic] couple projects"
>gets the empty interface wrong
>complains about the empty interface
nah

Fuck off already Google

thats not an argument

[coded]
unused, err := os.Open("nig")
unused = unused
[/code]

PHP is the PHP for retards you idiot. And no one forces you to use empty interfaces{} anywhere.