Neil Isaac
Neil Isaac
On second thought, reducing memory use is important for one of the applications I have in mind (storing media payloads in the queue), where storing a whole segment in memory...
I'm using Peek in an application with one consumer thread per queue (and potentially many writers via http handlers) for at-least-once delivery, so it's a solid use case. I'm considering...
@joncrlsn I'll take a stab at it
@LaurentMazare this would be pretty helpful
@stepancheg I was thinking along the lines of the first approach. Could we add a flag to override the crate/submodule to reference well-known types from in generated code?
@elfenpiff I'm not working with iceoryx presently (but hope to in the future!) so feel free to take this over.
@scentini this is the common case that was broken for me: https://github.com/bazelbuild/rules_rust/pull/1487/commits/17a00a30fd8066d415085bcd167993a615147edc
@scentini checks passed!
@asomers in general supporting something like `fn return_ref_from(value: V)` might allow for a more general solution by internally storing value as a `Box`. Unfortunately Option implements its own as_ref method...
I assume the main advantage of non-chunked writing is to implement zero-copy message writing? Is that an implicit requirement?