Editorial: Call GetWrappedValue with completion record's [[Value]] (#332

)

There's a confusion of completion records and language values in two
uses of the GetWrappedValue AO - quoting ECMA-262:

    Within this specification, the notation “Type(x)” is used as
    shorthand for “the type of x” where “type” refers to the ECMAScript
    language and specification types defined in this clause. [...]

An Object is a language type, a completion record is a specification
type.
This means that the "If Type(value) is Object" path in GetWrappedValue
would never be taken for these calls, even if the completion cecord's
[[Value]] field is an Object. Correct this by passing result.[[Value]]
instead of result (the completion record) itself.

spec.html

@@ -111,7 +111,7 @@ <h1>[[Call]] ( _thisArgument_, _argumentsList_ )</h1>
 			1. Let _wrappedThisArgument_ to ? GetWrappedValue(_targetRealm_, _thisArgument_).
 			1. Let _result_ be the Completion Record of Call(_target_, _wrappedThisArgument_, _wrappedArgs_).
 			1. If _result_.[[Type]] is ~normal~ or _result_.[[Type]] is ~return~, then
-				1. Return ? GetWrappedValue(_callerRealm_, _result_).
+				1. Return ? GetWrappedValue(_callerRealm_, _result_.[[Value]]).
 			1. Else,
 				1. Throw a newly created TypeError object associated with the _callerRealm_.
 		</emu-alg>
@@ -178,7 +178,7 @@ <h1>PerformShadowRealmEval ( _sourceText_, _callerRealm_, _evalRealm_ )</h1>
 				1. Suspend _evalContext_ and remove it from the execution context stack.
 				1. Resume the context that is now on the top of the execution context stack as the running execution context.
 				1. If _result_.[[Type]] is not ~normal~, throw a *TypeError* exception.
-				1. Return ? GetWrappedValue(_callerRealm_, _result_).
+				1. Return ? GetWrappedValue(_callerRealm_, _result_.[[Value]]).
 			</emu-alg>
 			<emu-note type=editor>
 				In the case of an abrupt ~throw~ completion, the type of error to be created should match the type of the abrupt throw completion record. This could be revisited when merging into the main specification. Additionally, in the case of a ~break~ or ~continue~ completion, since those are not supported, a TypeError is expected. There should be no ~return~ completion because this is a top level script evaluation, in which case a return |Statement| must result in a parsing error.