David Koloski

Moving this out of rkyv's 0.8 milestone

This is a subtle issue, but the correct type to call `rkyv::access` with is `rkyv::collections::swiss_table::index_set::ArchivedIndexSet`. I suggest using rkyv's `Archived` type alias instead: ```rust let _archived = rkyv::access::< rkyv::Archived, rkyv::rancor::Panic,...

Some quick poking around has refreshed my memory. This is a known limitation of the `Portable` trait, and is not a soundness issue. `Portable` does not apply recursively; it only...

Moving out of the 0.8 milestone

I'm surprised that `-Dmissing-docs` still triggers here even though these types are behind `#[automatically_derived]`. If we have to, I think a better approach than copying docs would be to generate...

All of the core APIs now have associated examples (`access`, `serialize`, `deserialize`, etc). The book will be updated with some more information soon.

Fleshed out some more of this in the book in 6c2e1e762e70ee07bd6b25c8f31ff0d36dcda283. Feel free to file separate issues if you have specific examples in mind.

Wouldn't this not be the case for `repr(Rust)` unions since the compiler makes no guarantees about how fields overlap? I think the inference can only apply to `repr(C)` unions.

`repr(Rust)` unions are still useful, but have a more restricted set of sound operations. For example, it's still perfectly sound to use external data to determine which field is set....

rkyv has `to_bytes` and `from_bytes` for this kind of functionality. For the reasons @w-flo mentioned, rkyv can't support `to_str` and `from_str`. You can read more about why rkyv's serialized format...