jtenner

How about comments like `@ts-ignore`? EDIT: This means that operation validation would be on the statement level instead of on the expression level. ```ts // @as-validate(: Reason) // @as-overflow-checks(: Reason)...

Another suggestion might be block level checks like this: ```ts // choose an intuitive block name here as_validate: { // this block generates overflow checks } ``` Also note that...

Honestly, implementing safe data types would be awesome. Please consider implementing a `u8_clamped` data type backed by `i32` which would make `Uint8ClampedArray` very easy to implement. It was mentioned that...

I was commenting on the idea of using a macro. Not the name :)

I think we need to override the meaning of call indirect.

How would this transform? ```ts function add(a, b): callback { return () => a + b; } ```

How does this work with function dispatch? For instance, let's say I pass the Closure Context out to js as a pointer. How can I re-call it?

Is there a way to make a table and add entries to it?

Well I'm thinking about aspect collecting function pointers. How will aspect need to work with the function pointers?

My guess is that passing around the closure context will cause problems with manually using call_indirect like aspect does. Also, this closure method doesn't handle multiple references to the same...