[go-nuts] Any way to let a new goroutine start to execute immediately?

If you want something to execute immediately, why start a new
goroutine? Just make a synchronous call.

- Evan

--

What have you run into that leads you believe that this is a problem?

-- Larry


--

Here are three options that I can think of:

http://play.golang.org/p/-Zg0fg4VEl

I don't think that option A is guaranteed to begin executing your
goroutine. It does in the example because there is nothing else to do,
but in another application there could be some other goroutine waiting
to run.

Option B may do what you want, but I believe that it could also switch
back to the parent goroutine at the close(ch) call. As a result, it
wouldn't really accomplish anything useful.

Option C seems reasonable, but there could be some nuances with
sync.Mutex that I'm not aware of.

What is the actual problem you are trying to solve? In general, it
shouldn't matter when the new goroutine begins executing. It will run
as needed to satisfy channel operations. Beyond that, it's hard to
predict or control. I think the plan is to introduce preemption into
the scheduler at some point, which will also alter goroutine
execution.

- Max

--

The definition of 'immediately' in a concurrent system is vague. If you
think you have a
need for something to happen 'immediately' then you've probably got a race
condition somewhere in your design.

I would say that the definition of immediately in a Von Neumann type computer is vague.

--