Things I hate about Go

Re:Things I hate about Go by chalst on Wednesday June 15, 2011 @03:15AM (#2656287)

> There are builtin polytypic functions, but you can't define your own.

This sounds like a first-release issue: getting type systems right in a way that allows you to grow your language is hard.

> Gorountines are just a hack for storing a continuation in a closure in functional languages.

No, I don't think this is fair. Firstly, controlling access to continuations makes sense, since they can be a world of woe. Second, continuations alone don't give you any parallelism: that CPS helps you understand the goroutines does not mean that the semantics of goroutines can be understood purely in terms of continuations.

See Shivers, 1997, Continuations and threads: Expressing machine concurrency directly in advanced languages (postscript), http://www.ccis.neu.edu/home/shivers/papers/cps-threads.ps

[ Parent | on HN ]

Re:Things I hate about Go by DanWaterworth on Wednesday June 15, 2011 @03:45AM (#2656327)

My problem is not that the runtime controls access to continuations, actually that's quite a nice thing for it to do. My problem is that it's implemented using segmented stacks, which is using more memory that just storing a closure.

[ Parent | on HN ]