On Fri, Nov 24, 2017, at 21:33, Dave Cheney wrote:
> > In Rust a thread has its own memory space and hence a thread cannot
> > reference data by reference of some other thread.
>
> How is this accomplished? Is there a prohibition against passing a
> borrowed reference between threads?
In
Ifaik rusts safety is compiler magic. Nothing special runtime you just
can't share stuff in dangerous ways. Syntax is horrible compared to Go but
who knows sometimes it can maybe be worth it.
On Sat, 25 Nov 2017, 05:10 , wrote:
>
>
> On Thursday, November 23, 2017 at
On Thursday, November 23, 2017 at 9:15:27 AM UTC-7, Haddock wrote:
>
> 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.
> In Rust a thread has its own memory space and hence a thread cannot reference
> data by reference of some other thread.
How is this accomplished? Is there a prohibition against passing a borrowed
reference between threads?
--
You received this message because you are subscribed to the
a browser engine need to support JavaScript,
so I think it make sense to write a browser engine in JS to support JS
itself.
if Go(or other language, web assembly...) can entirely replace JS in web,
then I think it will be wonderful,
BR fino
--
You received this message because you are
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