Closed ghost closed 1 year ago
Ah, thanks for the report. I'll look into this later today :)
Sorry, ran out of time. Will have a look during the week.
Thanks for looking into it. Please take the time you need.
To be clear, this issue is not blocking me in any way. I just happened to notice this and created an issue because getting this fixed may be good for your project in the long run. But it is of course up to you to decide whether this has any priority.
I've fixed this in 3.3.0, thanks again for the report!
The non-conforming TOML snippet
This testcase is part of
toml-test
: https://github.com/BurntSushi/toml-test/blob/master/tests/valid/table/array-implicit-and-explicit-after.tomlWhat you expected
This is a valid TOML document which should be parsed as
{"a": {"b": [{"x": 1}], "y": 2}}
The TOML 1.0.0 spec gives the following example as valid:
There is no reason why an implicit super-table should be treated differently when created by a table-array definition vs a table definition. Nothing in the TOML spec suggests that super-tables of table arrays should be considered as defined instead of merely implicitly created.
What you got
Environment
toml++ version and/or commit hash:
version v3.2.0, commit 698285d9b2f3f6756fcdab8b93f60352325764e1 on master branch
Any other useful information: