Yes, I know it's called "unsafe". Yes, I know that the official "contract" is that I should not rely on it. But realistically, can I rely on the following behavior?
I don't want to constantly be checking if a certain field is present or if its field value is not parsable for the expected type. For example,

auto value = object["key"].get_uint64_in_string();

would lead to value.error() being true if the JSON is something like

{ "key" : "" }

But I don't mind value.value_unsafe() returning 0 or whatever the default value is. For example,

auto value = object["key"].get_string();

if value.value_unsafe() gives me an empty string_view, that's fine by me.

Right now, I ran some tests, and it looks like simdjson does the above, like I want it to, and skimming through the code, it looks like the values are default-constructed. Can I rely on this?