LibJS: Correct SetMutableBinding fallibility bug in spec comment
This is an editorial change in the ECMA-262 spec. See: https://github.com/tc39/ecma262/commit/656f0cf
This commit is contained in:
parent
272cf3cbd5
commit
2fc9481bb6
Notes:
sideshowbarker
2024-07-17 22:41:14 +09:00
1 changed files with 1 additions and 3 deletions
|
@ -97,9 +97,7 @@ ThrowCompletionOr<void> GlobalEnvironment::set_mutable_binding(GlobalObject& glo
|
|||
// 1. Let DclRec be envRec.[[DeclarativeRecord]].
|
||||
// 2. If ! DclRec.HasBinding(N) is true, then
|
||||
if (MUST(m_declarative_record->has_binding(name))) {
|
||||
// a. Return ! DclRec.SetMutableBinding(N, V, S).
|
||||
// FIXME: Using MUST here breaks 22 tests in test262 (spec issue).
|
||||
// Example: `function f() { x = 1; } f(); let x;`
|
||||
// a. Return ? DclRec.SetMutableBinding(N, V, S).
|
||||
return m_declarative_record->set_mutable_binding(global_object, name, value, strict);
|
||||
}
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue