4 Commits

Include renames

Author	SHA1	Message	Date
LixenandClaude Opus 5.5	5c0a1c757a	v0.5.0 Unmapped reads any parsed value, UnknownKeys refuses what it names, decode errors name the key path ... * Unmapped reads any parsed value; decode errors name the key path Unmapped(data, v) names the keys of a value Parse produced that no field of v's type takes, a table inside a document included, so a caller holding a tree (after macro expansion, say) can refuse them as a Document's caller does; Document.Unmapped calls it. A decode error names where it failed by the key path the document spells, rooms[1].width or by_key."a b".width, rather than by Go type and field names and "index n" / "map key" segments; a key that cannot be bare, or runs past 32 bytes, is quoted and cut as parse errors quote one. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Rsnp29663hDvPHPua37MhN * UnknownKeys, the error naming the keys a caller refuses A caller that refuses what Unmapped names returns UnknownKeys(keys), "unknown key \"a\"" or "unknown keys \"a\", \"b.c\"", so every refusal words them alike. vif's settings already format their own; its FSM dialect would be the second copy. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Rsnp29663hDvPHPua37MhN --------- Co-authored-by: Claude <noreply@anthropic.com>	2026-10-26 03:30:55 -04:00
lixen	18ae215998	v0.1.3 bound parse memory and errors, conform better to toml spec for escpae and control chars	2026-10-03 23:14:11 -04:00
lixen	b59d068ff6	v0.1.1 decode hardening, round trip support, doc and test update	2026-09-28 14:05:12 -04:00
lixen	c8e23ff859	v0.1.0 initial commit	2026-07-13 02:45:49 -04:00