Rob ``Commander'' Pike - Go lang

http://www.u.arizona.edu/~rubinson/copyright_violations/Go_To_Considered_Harmful.html
"If you need to go to somewhere, goto is the way to go".

So the new hipster shit taking over now that the ruby is full of sexist rape supportors is Go!

http://www.u.arizona.edu/~rubinson/copyright_violations/Go_To_Considered_Harmful.html
It features a higher level of analness than seen in any programming languages that aren't based on french lambda calculi in particular:

http://www.u.arizona.edu/~rubinson/copyright_violations/Go_To_Considered_Harmful.html

Prepare to get shamed downvoted and patronized for asking how to turn "DECLARED BUT UNUSED VARIABLE" from an error into a warning: http://stackoverflow.com/questions/21743841/how-to-avoid-annoying-error-declared-and-not-used-from-golang

Here's some picks from the go implementation:

doc/go_faq.html:var _ = unused.Item // TODO: Delete before committing!
doc/go_faq.html: _ = debugData // Used only during debugging.
doc/progs/image_draw.go: _ = dirtyRect // noop
doc/progs/go1.go: _, _, _, _ = holiday1, holiday2, holiday3, holiday4
doc/progs/go1.go: _ = ErrSyntax
doc/progs/go1.go: _ = f
doc/progs/eff_unused2.go:var _ = fmt.Printf // For debugging; delete when done.
doc/progs/eff_unused2.go: _ = fd
doc/progs/error.go: _ = f


Despite this fucking ANAL BULLSHIT that even they have to work around, the language still has MOTHERFUCKING GOTO http://www.u.arizona.edu/~rubinson/copyright_violations/Go_To_Considered_Harmful.html

cmd/gc/walk.c comment out lines 67, 71

the follow tests will fail:

# ../test
# go run run.go -- typeswitch2.go
errorcheck typeswitch2.go : typeswitch2.go:43: missing error "declared and not used"
# go run run.go -- fixedbugs/bug373.go
errorcheck fixedbugs/bug373.go : compilation succeeded unexpectedly


You will now be able to program in peace.. unless you have to work on a codebase that has goto in it.

>>17
No I am not lel-kun_t. I'm also not particularly proud of this exchange.

>>10
I appreciate your work as a piece of art floating in the collection here we call /prog/. Does this settle the issue or do you still wish that I die? I'm inferring that what was written in >>11 was the cause of your textual attacks based upon the response pattern. I cannot gather this information from your post content because the post content only contained content that was to have a negative impact upon the wellbeing of the subject, the reader, (me), so that the reader would not feel content upon reading the content. I will further assure you that I feel very content upon reading the content of this thread and I will continue to contend to end the contest of content that contests contrary content in commencing communication catastrophes on caterday, the sabbath, and yesterday too.