You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our channels work send (Option, T) where T is the actual data and Option is a unique determininistic identifier for the data. We use an option as some threads may be spawned outside our spawn wrapper in some other crate (e.g. Rayon or Tokio spawns a thread). So these threads are assigned a DeThreadId of None. This means all information about the sender thread is lost. It would be useful for us to instead use a type like:
We might want to take this one step further and consider any thread sending channel messages from an "initialized thread" (one without a DetThreadId) to be a bug. This would simplify the cases we have to handle and would keep our deterministic gurantee straightforward.
Our channels work send (Option, T) where T is the actual data and Option is a unique determininistic identifier for the data. We use an option as some threads may be spawned outside our spawn wrapper in some other crate (e.g. Rayon or Tokio spawns a thread). So these threads are assigned a DeThreadId of None. This means all information about the sender thread is lost. It would be useful for us to instead use a type like:
In the case where threads are spawned outside our
std::thread::spawn
wrapper this would allow us to differentiate between:The text was updated successfully, but these errors were encountered: