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.

>>39
Sorry, you'll have to wait. I'm still having a hard time with >>38

Həmənſ ləck əgəncy. Þəy cən ənly də whətəvər Þə Eſtəbləſhmənt məkəſ þəm də.

>>3

they don't have IF/THEN/ELSE

FALSE!
usualy in most instruction sets the equal to if is something like a ifjmp, see http://www.unixwiz.net/techtips/x86-jumps.html

The presence or absence of syntax for goto is a nice shibboleth for distinguishing practical languages from languages that serve primarily as conversation pieces. Its presence in Rust is reassuring:

https://github.com/rust-lang/rust/issues/2216

>>44

Practical, huh? Well my personal scheme implementation found itself highly used (as in almost entirely with the rest being in good ol' C) in a certain experimental military project regarding non-gps methods of guidance and self-tracking. What about your rust or java?

>>44
Loop labels are the same as gotos now? This isn't what Dijkstra was talking about.

>>45
Calm down. If you needed loop labels you can easily shart out a macro to do the job with some simple combinator work. Using select/filter/whatever where appropriate is clearer anyway.

Rust's Iterator version is efficient: http://doc.rust-lang.org/std/iter/trait.Iterator.html#tymethod.filter

Java probably has a version that produces temporary objects that won't get GC'd until the next solar Eclipse.

Commander Kike

*farts*

wise fwom youw gwave

>>45

my personal scheme implementation

No one cares.

What is the point of having high level languages if everyone must implement their own?

the rest being in good ol' C

Which has goto, and for your particular application you probably had a use for it! What exactly is your point?

>>46

Loop labels are the same as gotos now? This isn't what Dijkstra was talking about.

They are completely equivalent, yes. Which is useful when dealing with people who treat the title of Dijkstra's paper like a religious edict.

>>49

They're not completely equivalent. Labeled break/continue provide the kind of structure Dijkstra found lacking with gotos. Which is useful when dealing with people who haven't read the paper.

>>44

shibboleth

Shalom!