Ryan Summers

@MathiasKoch I unintentionally editted your comment above, adding my reply here and reverting it shortly: > My use-case might be slightly off from miniconf's intended behaviour, but I am mostly...

It's just occurred to me that there may be complications in loading complex enums that expose their members as subfields. When you're loading the values from some external key-value storage,...

Your code example makes sense, so you'd have the following key-values in storage [("/foo", "Bar"), ("/Qux/inner", "9"), ("/Qux/other", "10")]. There's really two possibilities: 1. When attempting to set paths that...

> 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...

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.

I would expect the behavior to be as follows. I.e. when attempting to set `Foo::Qux`, `Error::Absent` is returned becaused `Foo::Bar` is present: ```rs #[derive(tree)] enum Foo { Bar, #[tree(depth =...

> Thanks for the discussion! I think we can draw a couple conclusions. Let me know what you think. > > * A node (i.e. a `Path/Indices/Packed`) can not simultaneously...

I don't understand why though. Could it not be the case where it is a leaf node when `depth1 = En1::Uni` and an internal node when using a different enum...

Ah that's right, I forgot that nodes are statically defined because all paths are present during iteration even if they're not run-time available. That kind of makes complex enums a...

Hmm, it's actually not possible to know what the depth of the outer structure should be when a generic depth is present. I.e. what if you have one item marked...