Conversation
| case reflect.Slice: | ||
| elem := v.Index(v.Len() - 1) | ||
| idx := v.Len() - 1 | ||
| if idx < 0 { |
There was a problem hiding this comment.
This seems odd to me. I'd expect something like a type check, so that we can confidentially return an error along the lines of "you cannot put an array of tables into something that is not a slice or an array" (there may be better wording 😅 )
There was a problem hiding this comment.
IIUC this index panic must be dealt with first. Perhaps my original example was not minimal enough. Consider this version, with the only change being an explicit [[A]] before [[A.B]]:
https://go.dev/play/p/rJqxTrNgONH
toml: cannot decode TOML array table into struct field struct { B struct {} }.B of type struct {}
Should the slice be expanded instead, so that we proceed along to this error ^?
There was a problem hiding this comment.
Here is a better version:
Panic: https://go.dev/play/p/ERU8JP5EldZ
No Panic with explicit [[A]]: https://go.dev/play/p/KL1MKmdEf6k
There was a problem hiding this comment.
Implicitly, A is a table. Adding an explicit [[A]] actually changes the structure of the document to make it an array of tables, so I don't think we can compare those.
To me, the logical path of the unmarshaler is:
- Is
Aa key in the current target? -> ✅ it's a field in the root struct. That value becomes the current target. - Is
Ba key in the current target? -> ❎ error: the current target is a slice, so B not a key; andAhasn't been marked as an array table.
The problem is, the unmarshaler doesn't explicitly tracks which tables are array tables or not for the sake of performance (except in strict mode). However, when it encounters an explicit array table, it guarantees that the slices have been expended as needed to be ready to receive a key lookup. This is because [[A]] is equivalent to {"A": [{}]} in json: https://go.dev/play/p/74TSvAtr8_R.
So, we should be able to use the fact that the unmarshaler is finding itself at a point where the container is a slice but hasn't been allocated as an indicator that the type are incompatibles, and document is possibly missing an explicit array table.
Towards #839
TestUnmarshalArrayOfTablesto reproduce