miniconf
miniconf copied to clipboard
quartiq
Rust serialize/deserialize/access reflection for trees (no_std, no alloc)
Update the `alive` indication for the following: 1. [x] Allow the python client to quickly determine what clients are already available (i.e. subscribe to some known topic to find all...
* Requested settings to be "owned" by the user, actual settings to be owned by the application, representing truth. * Supports reporting of quantized values, clamping * TBD: where to...
To properly pin protocol versions in downstream projects. * [ ] release the current client (e.g. as of 22feaa7) as 0.6.3 and migrate the downstream users * [ ] release...
Support getting (request to republish) a subtree. Host publishes the empty message to a topic that would otherwise result in `miniconf::Error::PathTooShort`. In the mqtt client the pseudocode would be something...
and potentially reduce, log+continue, elevate
Add an integration test that verifies the functionality of the `alive` topic publish via will and connection.
`impl TreeKey for (T, U) {...}` etc * Would be same depth of all fields * impl multiplicity: how many different types, how many fields, how many levels
* support for non-newtype tuple variants * support for record struct variants Should be reasonably simple now with Schema. split from #166
Investigate if there is any need for special handling of `Box`, `Rc`, `Arc`
https://github.com/quartiq/miniconf/blob/c741c31b8fcd5e8769861c16081f0d6895e019a2/miniconf_derive/src/tree.rs#L382 clashes with user `S`.