News for hackers. Stuff that matters.
Re:Go Rocks - How Can We Avoid Something This Bad In The Fut... by a_strange_guy on Sunday July 10, 2011 @04:19PM (#2748529)
(1) MLs allow to nest named functions. Go only allows named global functions, and lacks a feature that Pascal had.

(2) Someone has to do cleanup anyhow. Either the caller or callee. (I am no expert in calling conventions) Anyhow, isn't this practically free, because the stack is in the L1 cache?

(3) To implement lightweight threads (ala. Erlang, Go, Stackless) you already can't allocate your activation records on the C-stack. So the main cost for call/cc is already paid for. Besides, Go lacks any form of non-local jumps, so escape continuations alone (setjmp/longjmp) would already be an improvement.

Re:Go Rocks - How Can We Avoid Something This Bad In The Fut... by koenigdavidmj on Monday July 11, 2011 @12:48AM (#2749534)
> Go only allows named global functions, and lacks a feature that Pascal had.

    func main() {
    	bar := func() {
    		fmt.Println("Hello, δΈ–η•Œ")
    	}
    	bar()
    }
What do I lose by doing that versus having 'func bar()'?
Re:Go Rocks - How Can We Avoid Something This Bad In The Fut... by a_strange_guy on Monday July 11, 2011 @08:29PM (#2753057)
this:

    func global(some_arg_to_close_over Bar) {
    	func walk_tree(node Node) {
            ...
            walk_tree(left(node))
            walk_tree(right(node))
    	}
    	walk_tree(something)
    }