0.11 full release?

[AndrewGaspar]

Is there anything blocking a full 0.11 release? I'm considering adding this as a public dependency of another crate, but I'd be more comfortable doing it if there was a full release rather than just an RC.

[Enet4]

Thank you for reporting. If I recall correctly, we just wanted to be sure that everything works OK after these major changes to the API. @nabijaczleweli gets the call on whether we're good for 0.11 or we could use some more testing/documenting.

[nabijaczleweli]

I was mostly holding that on #54 for which I didn't have the capacity before, but now I've reread the entire doc and fixed what was broken, and all tests run and build on all cells.

That being said, I'd still like to see if @Enet4 spots something off-colour in the freshest doc, and I'll pull the trigger after his approval.

[AndrewGaspar]

I ended up just adding my own traits for this because I wanted the distinction between ToBytes and FromAnyBytes that this Pre-RFC describes: https://internals.rust-lang.org/t/pre-rfc-v2-safe-transmute/11431

[Enet4]

@nabijaczleweli Once you have the time, please feel free to release 0.11.0. In the meantime, we ought to be watching for progress at the safe transmute work group, not only to contribute to the discussion, but also to facilitate migration once a more well grounded solution to safe transmutation emerges.

[nabijaczleweli]

Confer v0.11.0

I've watched the repo, though it looks positively dead.

[Enet4]

Having had no activity in half a year does not necessarily mean that it's dead, maybe it just needs a bit of poking from some key players in the subject matter. The folks who work on these things are generally busy. I have nevertheless subscribed for any future interactions.