about go keyword

[rraammiinn]

is it used for another purpose ?

[medvednikov]

spawn is used for spawning threads
go will be used for spawning coroutines

[rraammiinn]

what's their difference ?

[medvednikov]

The docs cover that. Search for spawn.

[rraammiinn]

can we say spawn will spawn only limited available system threads and go uses program threads (threaded threads) that can be as much as you want ?

[JalonSolov]

No, because that would be incorrect. Spawn create system threads which are handled by the OS, any limits are whatever the OS imposes. Go will create coroutines, which are usually lighter threads handled by a runtime, and the number you can have will depend on many things.

[rraammiinn]

coroutines in python refers to asynchronous task ; in go it seems to be threads managed by program ( I'm not sure ) ; now what about v ?

[rraammiinn]

so I wana know that in coroutines whether program switches to another task only if cpu is freed by another task or it switches between them any way ( even if all of the tasks require cpu all of the time ) ?

[rraammiinn]

in python all the break points are declared using await keyword and there isn't any break point other than that , and there is multithereding in python that switches between tasks even if they don't free cpu ; now switching mechanism in v is similar to which of them ?

[rraammiinn]

I'm so confused about it .

[JalonSolov]

I recommend spending some time reading articles about the differences. It's a complex subject that a lot of people have spent a lot of time making it work.

TL;DR - unless you're writing hyper-performant code, don't worry about it. Use the spawn keyword for now, then use the go keyword when it comes back. Do your own benchmarks to see which one works best for you.

[rraammiinn]

ok , tanks .

[GavinAuey]

Goroutines are not bound to OS threads, which means that thousands of them can be created without causing any overhead. Goroutines are perfect for concurrent programming, as they can communicate with each other using channels.

[JalonSolov]

Goroutines do cause overhead, though it is usually less than system threads. System threads are fine for concurrent programming - the OS itself uses them. They can also communicate using channels (there's nothing magical about channels, they're just a data construct).