Mark S. Miller

Thanks! If the cst works (it looks like a great find!), I prefer it to the sourcemap path. With sourcemaps, the programmer is often looking at their original source text...

Actually, the current babel output seems to differ on more than whitespace, for example unnecessary parens, so that a correspondence verifier for babel output is no longer such a trivial...

> makes sense! From what I can tell, the intention of CSTs is more aligned with your goals. > > From what I can see on the readme, the flow...

> Need all the help I can get, I'm no security expert by any means! Hi @matthaywardwebdesign we've been working on this. In fact, we've been shaping JavaScript to make...

Please see https://medium.com/agoric/pola-would-have-prevented-the-event-stream-incident-45653ecbda99 by @katelynsills for a taste of our next major work in progress --- least authority module loading. This will be awhile, and is needed to integrate modern...

> an inconsistency with how var lists work I agree with this observation but come to a different conclusion. We should not use `var` for this.

Hi @bakkot , great list. Thanks for gathering it together. I'll use it to briefly state my current positions and point to the issue where this was discussed in more...

There are two main non-transparencies that I am aware of: ## Built-in methods see internal slots across realms For all built-in abstractions, like `Date`, that define instance with internal slots,...

The private symbol proposal here does not repair the above discrepancy. Attempting to use use private symbols as proposed would not only not repair the discrepancy, it would destroy transparency....

For :: to do the job of -> for hidden methods, we'd replace the hidden method declaration with a lexical function declaration as previously proposed. The first hidden method example...