WillAvudim
WillAvudim
It looks and feels great! Thank you for working on this!
We are building a high-perf large ML project in nodejs using tensorflow.js and a lot of custom computation modules. While majority of calculations are offloaded to CUDA, we still run...
Ran into the same issue and I confirm that `npm rebuild @tensorflow/tfjs-node --build-from-source` fully resolves it and lets me run on AWS ARM CPUs.
Ran into exactly the same issue: Works fine from the primary thread but crashes with "Error: Module did not self-register" in the worker thread. Node v20.9.0, everything is latest. I...
Any chances we could get this implemented?
I'm sorry, reading the description I couldn't understand: Is there a rule that highlights all places where an object with [Symbol.dispose] and [Symbol.asyncDispose] is assigned via a const or let,...
> * I have continued to argue that the [explainer’s real-world examples][] (and, indeed, any real-world codebase) show clear tendencies by developers to create poorly readable deeply nested expressions, instead...
I reviewed our project, which is about ~200 KLOC at this point, and I must admit I don't have truly great examples where the pipeline operator would be of substantial...
> > However, both LINQ and the SQL pipe syntax result in a code that doesn't necessarily flow through separate stages, and the result is compiled as a whole, without...
> Right, for that sort of expression analysis you need a context with bounds so the operations can be lazily transformed. Nothing about that is incompatible with pipeline (or any...