Graham Palmer

I wonder if you can use an atomic for the segment id such that when registering a new segment you do a `fetch_add` and it is guaranteed to be unique....

Ah but that does not work when registering with specific id's out of order... unless you also protect the individual entries with an `atomic`. And actually that might be all...

@elBoberido Because of the additional FFI benefits I'd be inclined to pursue this solution more over #2092 if it is deemed feasible. I'm also cautiously optimistic that it is a...

> Saying that, maybe we need to have a deep dive on the Rust design for the memory allocation. I'd be thrilled to do this 🙂 FYI I've been working...

I'm thinking something along the lines of an optional "filter" whereby a user can provide an optional list of shared memory segment names and the subscriber only maps those shared...

That time should work great for me 🙂

Was a pleasure for me as well. Regarding the design document and patches - - does it make sense to have multiple separate PRs referencing the same issue, - or...

> [mossmaurice](https://github.com/mossmaurice) assigned [gpalmer-latai](https://github.com/gpalmer-latai) [yesterday](https://github.com/eclipse-iceoryx/iceoryx/issues/2128#event-11555063049) FYI I haven't forgotten about this. I've just been a bit bogged down with other matters lately.

Having `on_construction` instead of exposing `getMemPoolInfo` would work nicely for me yes. That only really avoids exposing the last layer of lifting I did (and of course one could always...

Yeah I should have some latitude to work on the patch.