Emil Ernerfeldt
Emil Ernerfeldt
Closed in favor of: * https://github.com/rerun-io/rerun/issues/7588
@jprochazk I summarized my understanding of `rav1d-rs` in this issue - feel free to edit/comment: * https://github.com/rerun-io/rerun/issues/7575
This is blocked by: * https://github.com/rerun-io/rerun/issues/8056
Does arrow bottom out in https://crates.io/crates/bytes ? That would be useful for storing RC-counted references across crates. Otherwise we have to consider a few different alternatives: * `re_mp4` uses `bytes:...
I think the best path forward is to change `re_mp4` to store byte ranges (`Range`) rather than the raw bytes, and then have `re_video` (or `re_renderer`) have some sort of...
The vast majority of the time used by `Mp4::read` is allocating memory for each sample (see https://github.com/rerun-io/re_mp4/pull/11). If we instead store byte ranges, all that goes away. This mean this...
Does this affect the dataframe view?
We should be compatible with any glibc 2.17+, see: * https://blog.rust-lang.org/2022/08/01/Increasing-glibc-kernel-requirements.html * https://github.com/rerun-io/rerun/issues/7788 * https://github.com/rerun-io/cpp-example-vrs/pull/15
My two cents: My base expectation of any crate is that `cargo` should be enough to build it. Anything else is a big red flag. As for `enable_type_names` and `bytes`:...
That's what we do in Rerun too: devs run a command to regenerate the rust code, and the check that in to git. We also have a CI step to...