jakobkummerow

My suggestion is to disallow non-nullable reference types in JS interop. But apparently some folks think that we should support everything everywhere... in which case we'll have to answer these...

AFAICS this appears to be a rather questionable change: - Per [this comment](https://github.com/nodejs/node/issues/44046#issuecomment-1200151261) in the associated bug, this would have the effect of completely hiding `kGCTypeProcessWeakCallbacks` performance events, which would...

Cool stuff. You asked whether this is "useful", that's not really for me to decide. Personally, I don't think it's useful to show bytecode or unoptimized code. My reasoning is:...

> is turbolizer a supported tool from v8? Define "supported". It's a tool made by V8 and for V8. We'll keep maintaining it as long as we find it useful...

I think we can close this after the ion-js fix.

I would suggest that the learnable experience is that this works just fine as a library. No need to add yet another feature to the language just for a few...

Wouldn't all five of those points be addressed by having a standardized (or otherwise somehow "officially blessed") library? Besides, a particular counter-point on the first point: the download size wouldn't...

"has some highly optimized implementations" is too vague to be useful as a statement. For example, large integers (~ BigInts) "have some highly optimized implementations" (e.g.: GMP, MPFR, Flint, OpenJDK),...

JSBI author here. Not interested. BigDecimal libraries should be separate from BigInt libraries.

It has been pointed out to me that I should clarify: I am totally in favor of standardizing a library for BigDecimal. My concerns as laid out above apply specifically...