@alexbuzzbee ehlol wolrd
Oops, sorry, next time I'll use #Rust
@janriemer AFAIK Rust wouldn't stop that.
@alexbuzzbee Yes, you are probably right!
I'm not really familiar with SIMD much less SIMD in Rust, but it seems you need `unsafe` to use certain SIMD-features that are available on certain architectures:
https://doc.rust-lang.org/edition-guide/rust-2018/simd-for-faster-computing.html
I'm not sure how this (unsafe) will affect thread-safety, but generally one can say:
While #Rust guarantees thread-safety during compilation, it doesn't mean your software is free of concurrency bugs.😉
Hello world
Oh, apparently it has worked this time around.I wont try again😜
@janriemer The other problem to consider is that, again as far as I know, Rust doesn't serialize IO, so if you have several threads writing stuff at once it'll still get interleaved.
@veer66 @brombek Thank you for the resources. So Rust indeed locks it. Thank you!🙂
Also have a look at the following response by Sergey:
https://mastodon.technology/@bugaevc/106657442154323110
@brombek @janriemer @alexbuzzbee Or Rust stops them all by locking? It is safe but not parallel? https://github.com/rust-lang/rust/blob/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/io/stdio.rs#L852