Mark S. Miller

agoric-sdk compat testing underway at https://github.com/Agoric/agoric-sdk/pull/9201 , with pound-endo-branch: markm-to-throwable-2 and force:integration label

@kriskowal I hopefully marked this as next-release because it would be really nice for that to happen, and I also hope this is an easy enough review to not impose...

CI at https://github.com/Agoric/agoric-sdk/pull/9201 failed due to the presence of `patches/@endo+exo+1.4.0.patch` , which seems will need to disappear in the next sync anyway. So I just added to it a removal...

CI is still failing a lot, but none of the failures seem to have anything to do with this PR.

Restaged https://github.com/Agoric/agoric-sdk/pull/9201 on https://github.com/Agoric/agoric-sdk/pull/8774 and trying again. I see that https://github.com/Agoric/agoric-sdk/pull/8774 is not green either. But if https://github.com/Agoric/agoric-sdk/pull/9201 only has the same failures as https://github.com/Agoric/agoric-sdk/pull/8774 , I'll count that as...

Reviewers, because it is possible in theory that some old code was depending on an exo throwing something that would now be classified as a non-throwable, this PR is in...

> that we could build the .js from .ts. That would either require us to * audit the ts-to-js compiler for preservation of our security properties, and re-audit when the...

> Whatever is in that audit could be automated, no? Do we have a test suite of security properties that must be maintained by any syntax transformer? If not, that...

> But I like what I think you're proposing: moving the JSDoc to TypeScript files. Good. Let's do that for now while we continue exploring other options. Thanks!

> I recall a naming concern with @erights and I’m not sure we settled that. Anyone remember what that was?