David Koloski
David Koloski
`array.map` is stable as of rust 1.55, so this feature should no longer be needed if you bump the MSRV to 1.55.
Hi! Thanks for all your work on bebop, it's a really exciting new framework. I'm working on integrating bebop into the [rust serialization benchmark](https://github.com/djkoloski/rust_serialization_benchmark). The code is structured like this:...
It appears that [`validate_utf8_basic`](https://docs.rs/simdutf8/0.1.3/src/simdutf8/implementation/x86/mod.rs.html#14) and similar functions trigger [a mislink](https://github.com/rust-lang/rust/issues/81408) on Windows with lld and thinlto. This is not a terribly uncommon combination, so it may be worth exploring alternatives...
Requires https://github.com/hyperium/h2/pull/614 before this will compile. We can avoid a transmute and some questionable code by using a specially-crafted conditional `Send` impl. `Sendable` and the impl are inside a `const...
The names `(fp, fo)` actually stand for `field_pos` and `field_out`, but are referred to in the docs as `offset` and `pointer`. Unifying these naming conventions would help alleviate confusion.
A macro like `if_strict!(t)` and `if_strict!(t, f)` would be good to export from rkyv. This would allow strictness to propagate downstream directly from the core crate and remove the need...
This should be pretty straightforward. The iterator implementation should yield a single element if `Some`, or `None`.
An upstream Rust bug is causing impl conflicts in downstream crates with this specific pattern. We should replace these uses with explicit types to work around this issue. Upstream issue:...
While enum discriminants can be assigned to the unarchived versions of types, the archived versions cannot be explicitly enumerated in the same way. This means that reordering is a breaking...
I'm trying to get a better idea of what the roadmap for rkyv should look like for v0.7 and beyond. As just one person with a very particular use case...