I assume this was just an oversight; we handle throwy getters already, but not throwy proxy traps for GetOwnProperty. This can only be exercised if the first call to GetOwnProperty succeeds and returns an iterable and then a later one throws, but that can happen.
I assume this was just an oversight; we handle throwy getters already, but not throwy proxy traps for
GetOwnProperty. This can only be exercised if the first call toGetOwnPropertysucceeds and returns an iterable and then a later one throws, but that can happen.