Kevin Gibbons

`_value_` gets unwrapped by ReturnIfAbrupt already; the problem is that the new logic is failing to account for ReturnIfAbrupt and friends. That said, I'd write the above code as ```...

You can't use `!` because it might actually be abrupt, at least as currently written. But yes, you can unwrap with `Set _iteratorResult_ to ? _iteratorResult_.`, and that would also...

(I actually kind of [want to get rid of ReturnIfAbrupt entirely](https://github.com/tc39/ecma262/pull/1573#issuecomment-1913042895), though we'll still need IfAbruptCloseIterator and IfAbruptRejectPromise.)

No, but you can `Set _value_ to ? _value_`. Or if you already know that `_value_` is definitely an abrupt completion, you can `Return ? _value_`.

We only use `Perform` when invoking AOs or SDOs.

Yes, that option was removed for simplicity since it is trivial to do in userland, though we could always add it back. See [some discussion on the Python tracker](https://github.com/python/cpython/issues/73613) of...

The default will definitely continue to be including padding. Most uses of base64, url or otherwise, are not in internet specifications, and many decoders enforce presence of padding.

I'll put something together for the next meeting. Thoughts on naming here? [W3C design principles](https://w3ctag.github.io/design-principles/#optional-parameters) say that optional boolean arguments should default to `false`, so it would have to be...

Opened https://github.com/tc39/proposal-arraybuffer-base64/pull/60 and put it on the agenda for next month.

The default behavior for padding is not going to depend on the alphabet used, and the default when no options specified is to include padding, to match `bota`. So yes,...