Native Tensor support

2018-01-26 Thread Robert Eisele
Hello, Allocating multi-dimensional arrays in Javascript is only possible by building each dimension individually. In addition to being a very tedious job, a developer has no control over memory usage, which in general is likely to be very high. Seeing an array algebraically as a vector, typ

Re: Native Tensor support

2018-01-26 Thread Isiah Meadows
Two questions: 1. Would APIs that operate on existing data types (rather than tensors) work just as well? 2. Could there instead be a kernel-like API that could work on things independently? Lower level APIs that enable equivalent high-level constructs is a much better place to start. And two com

Re: Native Tensor support

2018-01-26 Thread Boris Zbarsky
On 1/26/18 10:49 PM, Isiah Meadows wrote: Applying DOM changes from a static change list is an embarassingly parallel\* problem. Only if you know there are no overlaps in terms of the nodes involved. And you ignore mutation events. And you ignore the fact that mutation records expose your or

Re: Native Tensor support

2018-01-26 Thread Isiah Meadows
I'm speaking from the framework's side. Yes, I did gloss over certain complexities and constraints, but yes, it's almost there in practice. 1. If they don't expose the node through a ref or something, and no event handlers exist, they could just assume (unsafely) you don't reference it, and act ac