Concurrency in Rust and Go are completely different things. In Rust a thread has its own memory space and hence a thread cannot reference data by reference of some other thread. The rational behind that is security. Also, a thread in Rust is not lightweight, but a full-blown OS thread. So there is no CSP in Rust as in Go and therefore there is little to compare between Rust and Go concerning concurrency. AFAIK, there is some crate in Rust that adds some minimal support for coroutines, but I don't think its used in Servo.
Am Donnerstag, 23. November 2017 09:04:09 UTC+1 schrieb Anssi Porttikivi: > > How would this look, if implemented in Go? Is there anything to learn from > Rust "fearless concurrency"? What are the goals and complexity trade-offs > of the two languages? > https://blog.rust-lang.org/2017/11/14/Fearless-Concurrency-In-Firefox-Quantum.html > > When and why would there be a browser engine in Go? ;-) Some interesting > projects to compare to are > - Servo (rust) https://github.com/servo/servo/ > - 3S (haskell) https://hsbrowser.wordpress.com/3s-functional-web-browser/ > - LURE (lua) https://github.com/admin36/lua-LURE > - Weasy (python) https://github.com/Kozea/WeasyPrint > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
