pub fn own_enumerable(v: &Value, key: &str) -> Result<bool, String>Expand description
Is key an own ENUMERABLE property of this proxy right now? One
getOwnPropertyDescriptor trap call, which is what for-in runs per key at
the moment it visits it (14.7.5.10) — own_enum_string_keys answers the same
question for every key at once, which is the wrong shape when the body
between two visits can delete a key or flip its enumerability.