Mathias Koch
Mathias Koch
Guess this died out again? @eldruin @dunmatt
I started an implementation of general enum support, but I think we might need to discuss slightly how it should work :p ### Basic enum keys For instance, a simple...
> Switching between variants can later be implemented via some "tagging" field outside (adjacent/external/internal like serde) that then implements the switch in its handler. Yeah, I thought about these as...
> I'm not certain it's actually possible with Miniconf to guarantee that variants could be swapped. I think this is only possible if there's a single leaf within the enum...
> What's the serialized unit type? Might be "" or "()" I would think this would work like serialized json, where unit types act as a string serialization on the...
> I'm not sure I'm completely following what you mean here. Do you have a small example? I can try. Building on your example: ```rust enum Foo { Bar, #[tree(depth...
> If not, I'm unsure how miniconf could apply half of a `Qux`, (i.e. `inner` is specified, but `other` has not yet been defined) But wouldn't this be exactly the...
Alright, so to sum up so far, we are down to a few bigger (uncovered) issues here? 1. How would it work, having a path simultaneously be a leaf and...
Makes sense overall. The only one I am seeing a slight issue with is the last one. For my application, I need to be able to load the full struct...
> You could also handle this outside of miniconf by detecting the `Error::Absent` being returned and potentially then updating the enum based on the key and reapplying it for now....