Reasoning behind some of the JSON Schema restrictions

[amiasato]

I'd like to have some more insight on some restrictions that the new constrained decoding API has for JSON Schemas. More specifically, why are the following disallowed:

• Generic objects (even plain str->str maps are not valid fields)
• Examples (comprehensible place to employ few-shot prompting)
• Defaults

None seem to be limitations with CFG design, so I guess they are motivated by issues with the model. It would be super nice to have them possible to enable (maybe some warnings, disabled by default, idk).

Thanks