runtime.Gosched usage is likely to lead readers astray

[raggi]

While this might well be the shortest way you found to demonstrate the output you wanted, training users toward this function stands a good chance of them trying to use it to solve early problems it is not suitable for.

[thewhitetulip]

this one right?

func say(s string) {
    for i := 0; i < 5; i++ {
        runtime.Gosched()
        fmt.Println(s)
    }
}

The thing is, this chapter is adapted from the book by @astaxie.

I will make some modifications to the description.

[thewhitetulip]

@raggi I now have time for looking into this, do you suggest any alternate mechanism that is simpler for new comers to understand?

[raggi]

It's a fair question. The thing is that since GOMAXPROCS is now defaulted to a higher value and most users will not be on single core systems, I'm not sure you'll need this in order to demonstrate parallelism, it just won't be even. In future versions of Go, this may not be even anyway.

Maybe you'll want to set GOMAXPROCS to 4 just to be certain, but that's also mostly unnecessary.

[thewhitetulip]

Okay, so shall I remove this example and put in a basic one if it isn't present

func main(){
    go say()
}

And remove the example you are talking about?