On Mon Mar 18 13:51:11 2024 +0000, Rémi Bernon wrote:
Imo it makes it more awkward to use the shared read/write macros. They assume an object with its header to be passed, and using them for the session implies that it *has* to be an object. Faking it by using a different struct with just a seq feels wrong. If the session being an "invalid" object feels too awkward I'd prefer to simply set its id to be non-zero instead.
Setting the ID to -1 works for me. (It's guaranteed to be distinct from any other ID, and stands out from the rest.)