Mark S. Miller
Mark S. Miller
Hi @mhofman , I've co-assigned myself to this.
Huh. Testing just now, it was added sometime between Node v18.19.0 exclusive and Node v20.18.3 inclusive.
Because the observable change of #2700 that this PR allegedly fixes is only observed interactively when running the vscode debugger, this PR does not add a test case verifying the...
Closing due to @boneskull 's observation at https://github.com/endojs/endo/issues/2891 that `new` is required for user-written Error subclasses.
Please see stage 2.7 proposal https://github.com/tc39/proposal-immutable-arraybuffer with shim at https://github.com/endojs/endo/tree/master/packages/immutable-arraybuffer . The proposal is also natively implemented by Moddable's XS engine, passing all the test262 tests in the test262 PR...
Why not just implement the [Immutable ArrayBuffers proposal](https://github.com/tc39/proposal-immutable-arraybuffer)?
See also https://github.com/Agoric/agoric-sdk/issues/10375
Putting this back into Draft until I make some changes: - Split the PR into two staged PRs. 1. change all remotable creation to avoid symbol-named methods, with the possible...
> since the method names `constructor`, `prototype`, and `then` create attack surface. Yes for `constructor` and `then`. What's the problem with a remotable method named `prototype`? (I admit it is...
Re `constructor`, `then`, and `@@asyncIterator`, very clever mapping these 1-1 to JS-only symbols. I had thought any solution to these would need a Hilbert hotel. But since there's no other...