We implement this for first and second order tensors in
gonum.org/v1/gonum/mat[1], which you are welcome to borrow from to
extend to third order. Our slice operation[2] is in principle non-
allocating (though we do allocate a container for generality - a non-
allocating version would simply not return the pointer type for the


On Sat, 2017-08-12 at 07:14 -0700, chatrapathi.ak...@gmail.com wrote:
> So I've written a small Tensor library for purposes of various
> computations 
> inside a hardware product that my startup is working on. I've
> implemented 
> in the library, the functionality to slice a matrix similar to matlab
> using 
> a proxy. The implementation, I have works just fine and does exactly
> what I 
> want, albeit with one hiccup, every time I slice the matrix, it
> allocates 
> for the proxy. This caused a problem inside hot loops. Hence, I
> implemented 
> the same functionality by allowing the user to pre-allocate the proxy
> and 
> slice the matrix into it, thus eliminating the problem. However, I'd
> like 
> to know if the size of the proxy can be reduced any further or a
> more 
> efficient way to achieve the same functionality? Relevant runnable
> code can 
> be found here <https://play.golang.org/p/TQMdNLBbCi>

You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to