Michal 'vorner' Vaner

Reading the hazard-pointer approach, it does look interesting. But I'm a bit nervous about two things ‒ the fact that an update may force a reader to loop (therefore the...

Thank you for your answer. It is probably by a lack of knowledge of the code that I don't see how having a different error variant when an unexpected EOF...

I see the example lives in the shred repository. Might this be caused by specs re-exporting the types? I'll try to read through that and try to improve the docs...

I don't think crossbeam channels are the appropriate thing here (because they can be set up to lose the newest, but not the oldest value, you need just one value...

Right, that's what I mostly wanted to avoid. I don't know if it's just my sense of engineering elegance, but having to do some kind of export to other format...

> Doing this via mapping the events identically on all sides is generally known as the lockstep, or Deadman's simulation, and is also quite popular for certain types of game...

Hmm. That doesn't really solve my use case :-(. First, I'd still need to know/force the user to provide the right constant. But more importantly, it wouldn't allow me to...

Unfortunately, this won't work. I can (in a branch) set the number of lanes based on `const usize`, but I still haven't figured how to do an alignment based on...

My intention was to just provide the `type V = ...` that can be used internally. I can do it with a macro and `#[target_cfg]`, but that doesn't work with...

Yeh, that's as I said almost doing the multiversioning by hand. That doesn't seem to be very ergonomic for the user :-(. I mean, if there's no easy way to...