dcodeIO

Results 484 comments of dcodeIO

Thanks for the ping! Iirc, one blocker could be exceptions thrown in the interpreter, which do not only indicate a hard error a release build could just expect never to...

Just a quick note: I think if we'd disable the precompute pass, `asc` would still not work because it depends on `ExpressionRunner` so much, which uses the same underlying infrastructure...

It is necessary, sadly. In AS, we do not have `#ifdef` for example, but instead have a mechanism to do things like `if (isString() && someLocalThatIsActuallyConstant) {` (or arbitrarily complex),...

For reference: https://github.com/google/protobuf/blob/master/src/google/protobuf/timestamp.proto protobuf.js uses so called wrappers to provide additional functionality on top of the raw data types (seconds, nanos). There's one for [any](https://github.com/dcodeIO/protobuf.js/blob/master/src/wrappers.js), but none for timestamp yet.

The usual way for changing how files are resolved is to [override resolvePath](https://github.com/dcodeIO/protobuf.js/blob/master/src/root.js#L54). The default behavior differs from how the official implementation does this for no particular but historical reasons,...

I do like the idea of replacing the JS plus separate typings with TS plus generated typings. I'd probably go even further and also generate the API docs from tsc's...

Iirc there has been some discussion about this in the past, where it was noted that the CLI tools could provide threading under Node.js - when specifically built for it....

The CLI tools shipped with the package, e.g. wasm-opt, are multithreaded now iiuc.

Perhaps an idea: In case of a `NONCONSTANT_FLOW` as the value of a `drop`, utilize `EffectAnalyzer` to see what caused it, and if the only side effects were local or...

Yeah, in typical optimization scenarios this isn't an issue, just when using `ExpressionRunner` as an API, via C, while still generating code. That's kinda the new use case of making...