Mark S. Miller
Mark S. Miller
If the answers to such questions is similarly yes, then compiling actual Jessie to AssemblyScript would be very cool.
For all four of these, I think we should change the definition of Jessie to allow them. I'll comment on each of the issues you link to.
No, after reading https://github.com/Agoric/Jessie/issues/29 I changed my mind. It is correct. We should implement and use that std library so that we don't have unnecessarily unhardened objects, like instances of...
I think we should revise the definition of Jessie to allow this.
I think we should revise the definition of Jessie to allow this.
Not just `Promise.all` but all four, overloaded exactly this way. I favor that it operates on exactly the enumerable own properties, whether string-named or symbol-named, like `...` and `assign` do....
This is now Ready for Review. PTAL
> As this is not a pure refactor, I would like to fully separate the changes that have zero risk from the changes that have non-zero risk. Done. The zero-risk...
> For my use cases, unsafe-keep-and-inherit is enough, Excellent! > Can you give an example what this might be look like in the user land? ```js const compartment = new...
> Adding %Reflect%.metadata to the permits might introduce a hazard in the event the Reflect is later hardened and endowed. Do we need an option? If the `reflect-metadata` package runs...