Replies: 1 comment
|
Please post this in our forum instead. Thank you! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
At this point it doesn't seem that Mojo is exposing any access to threads or provides public implementation of parallelize or other algorithm functions.
I really wonder - are there any docs/discussions/ideas about how the thread-safety enforcement (if any) would Mojo have?
In Rust we have Send/Sync, pinning for async stuff, etc.
Swift ended up having single Sendable trait, but it lacks the ability to return/store references, so its model is simpler than Rust's.
Mojo looks much closer to Rust in terms of reference semantics (with the difference that when you want to store them - you have to convert them to pointers), so I wonder whether there were any discussions about thread-safety topics in Mojo.
All reactions