Sway Version: { "human_readable": "1.10.1", "variant": "sway", "major": 1, "minor": 10, "patch": 1, "loaded_config_file_name": "\/home\/gustafla\/.config\/sway\/config" } bemenu v0.6.23 wmenu 0.1.9...

Thanks. That's good to know. Well, I've been googling around if there's any alternative due to a bug(?) affecting me immediately: human_readable flag does not get carried through · Issue #2704 · serde-rs/serde · GitHub , and was just wondering if I could derive a different set of trait or something for some niche serde alternative. OTOH, I remember there were also some limitations for XML (not being able to represent some stuff), and around things like `Option<Option<_>>`, etc. but these are minor corner cases and a distant memory. When looking through musli musli - Rust I've noticed: > **We use GATs** to provide easier to use abstractions. GATs were not available when serde was designed. Also, when reading about musli's "modes" and thinking about that bug affecting me right now, it did occur to me that it would be great sometimes if serde could carry over more information about serialization format being used. E.g. would be nice if serialization code for my datatypes could detect that we're e.g. deserializing to CBOR and special case it because _reasons_. There are things like QR codes etc. where customizations like these are handy. Though maybe I could emulate using some thread-local context variable ...