Vitali Lovich

Would this also be the solution for math operations not generating implementations that handle references? ``` let e = Example(3); assert_eq(Example(1) + &e, Example(4)) ``` Obviously non-sensical in the toy...

One thing I’ve been thinking about is having separate QUIC connections per CPU and making it the responsibility of the application logic to manage sharding through a pool of connections....

Work stealing isn’t about how you handle CPU overload. You are correct that back pressure is how you need to handle that. Work stealing is about making sure that when...

Not sure if exposing `trim_to_size` is all that's needed although I don't know if that'll actually work (haven't tried it out).

No direct I/O via `DmaFile`. I'm managing my own buffers directly so the stream API isn't really useful for my purposes. Specifically, I have no problem creating holes with `write_to`....

That doesn't actually help because you're still going to get write amplification to the flash. Most Linux filesystems (XFS, ext4, btrfs AFAIK) will all write a much smaller amount of...

Also `fallocate` isn't exposed itself AFAICT. It's only exposed within the crate so that `pre_allocate` can invoke it. `pre_allocate` itself has the surprising (wrong?) behavior that calling it on an...

Not working on this project anymore so cleaning up a bug I doubt will have any forward momentum.

How would you implement `dma_serialization_size` in a serde world?

Also, I'm having trouble on 2 fronts. The first is that this fails to compile: ``` /// Like [`BinaryFuse16`] except represents a reference to a filter. #[cfg_attr(feature = "serde", derive(Serialize,...