V: Coroutines

[nnsgmsone]

I found that the coroutine of v is directly called pthread_create. I think it is possible to add user-level coroutines, so that more energy can be injected. Perhaps can learn from golang's approach and add a runtime. . .

[spy16]

Implementing coroutines (similar to Go approach) has always been the plan and is in the roadmap. See https://vlang.io/docs#concurrency

[nnsgmsone]

ok

[spytheman]

@nnsgmsone what does 'more energy can be injected' mean in this context?

[nnsgmsone]

@spytheman make the routine more useful

[joe-conigliaro]

As far as I know this was the intention all along, they were Implemented that way to begin with to have something working.

[gslicer]

I think the use of subroutines is very limited in contrast to what threads can offer (as long as implented e.g. with the "actor" paradigm, without any semaphores/locks)... so threads shall be still supported.

See this statement:

Why create threads when there are coroutines?

Coroutine methods can be executed piece by piece over time, but all processes are still done by a single main Thread. If a Coroutine attempts to execute a time-consuming operation, the whole application freezes for the time being.

Threads are different. The execution of separate Threads is managed by the operating system. If you have more than one logical CPU, many threads are executed on different CPUs. Thanks to that, any expensive operation will not freeze your application.

[dumblob]

@gslicer don't worry, there will always be the unsafe package with all primitives to create your own threads with your own condition variables, mutexes, locks etc. I think the topic here is not about this though. I think it's about having a builtin primitive for concurrency and that's fully covered in https://github.com/vlang/v/issues/1868 .

Thus I think this topic can be closed as it got fully superseded by https://github.com/vlang/v/issues/1868 .

[gslicer]

@gslicer don't worry, there will always be the unsafe package with all primitives to create your own threads with your own condition variables, mutexes, locks etc.

As long it's "unsafe" I'm clearly worrying :)

[nnsgmsone]

@gslicer I think it's easy to achieve the effect of an actor with the routine and channel.For example, a library I wrote myself is such an effect.

[crthpl]

Will there be a compiler flag to make go start a new thread like it does now?