Go et erlang sont très différents. Je ne pense pas qu'on puisse considérer go comme un système à acteurs.
Non mais on pourrait le simuler si je ne m'abuse.
D'ailleurs je disais ressemble car si on lit la page wikipedia à propos Go (concurrency: goroutine and channels), on trouve des affirmations de la sorte:
The language specification does not specify how goroutines should be implemented, but current implementations multiplex a Go process's goroutines onto a smaller set of operating system threads, similar to the scheduling performed in Erlang.
ou encore:
The existence of channels sets Go apart from actor model-style concurrent languages like Erlang, where messages are addressed directly to actors (corresponding to goroutines). The actor style can be simulated in Go by maintaining a one-to-one correspondence between goroutines and channels, but the language allows multiple goroutines to share a channel or a single goroutine to send and receive on multiple channels.
C'est issue de la même source cependant.
Mais oui le modèle de concurrence diffère, je suis d'accord.
[^] # Re: Rust et SIMD
Posté par wolowizard . En réponse à la dépêche Faut‐il continuer à apprendre le C++ ?. Évalué à 3.
Merci,
Non mais on pourrait le simuler si je ne m'abuse.
D'ailleurs je disais ressemble car si on lit la page wikipedia à propos Go (concurrency: goroutine and channels), on trouve des affirmations de la sorte:
The language specification does not specify how goroutines should be implemented, but current implementations multiplex a Go process's goroutines onto a smaller set of operating system threads, similar to the scheduling performed in Erlang.
ou encore:
The existence of channels sets Go apart from actor model-style concurrent languages like Erlang, where messages are addressed directly to actors (corresponding to goroutines). The actor style can be simulated in Go by maintaining a one-to-one correspondence between goroutines and channels, but the language allows multiple goroutines to share a channel or a single goroutine to send and receive on multiple channels.
C'est issue de la même source cependant.
Mais oui le modèle de concurrence diffère, je suis d'accord.