Writing my own init with Go

Re:Writing my own init with Go by pcwalton on Tuesday February 09, 2016 @01:38PM (#11067582)

Yeah, that's basically having the runtime advance to the next GC safe point before running the handler. It's not direct control over signal handlers, but it's fairly low overhead. I guess Go could do this too if it wanted to. I don't think it works for fork though.

[ Parent | on HN ]

Re:Writing my own init with Go by chubot on Tuesday February 09, 2016 @02:41PM (#11068144)

Yeah the problem with Go and "async processes" doesn't have to do with GC -- it has to do with M:N threading. I'm glad Rust abandoned M:N threading.

Though it is definitely a killer feature of Go to write in a blocking style rather than in a state machine style... but I feel that there might have been a way to do it without baking it so hard into the runtime (?). Maybe like coroutines in Python, which run on a single thread and are optional.

M:N threading causes a lot of other complications too, like calling from C to Go, etc.

[ Parent | on HN ]