-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dotted key ordering isn't always preserved #163
Comments
If/when we add position information, a next step is to see if we can infer an inserted values position based on the parent dotted table. This would have us automatically organize new keys as is encouraged in the TOML spec |
Has there been any progress on this? |
Generally, if there were, they'd already be posted here or in a linked issue Overall, the use of dotted keys seems small and alt ordering being even smaller as its non-idiomatic, that this hasn't been a priority for me. If someone else wants to pick up the work, they are welcome to. |
Thanks, I was just curious as I'm thinking about making Python bindings. |
Hi! Drive by question: |
As this is isn't a focus area / priority of mine, it will be up to you to do some leg work on investigating this. |
Looked into it and the cause seems to be the recursive way the the structure is stored. |
I've just raised a PR to fix this - #808 I won't pretend its the most elegant solution, but it does seem to work. Feedback welcome, I don't mind taking a new approach; I'm honestly not the most experienced with rust. |
gets turned into
The text was updated successfully, but these errors were encountered: