Use Rust's ndarray library more efficiently in the interpreter

[gussmith23]

We use ndarray as our tensor representation, but we don't use it very efficiently. Specifically, we copy data everywhere, for nearly every operation. The ndarray library is smart; it can do many of the operations we need to do without copying data, if only we understood how to use it well. There are also opportunities to contribute back to ndarray, if we find something we'd like to be able to do that they haven't yet implemented. From what little I've dug in their source code already, it seems like these opportunities might be abundant, and contributing shouldn't be too hard!

[gussmith23]

@hypercubestart This one mostly involves taking a look at the ndarray library and using it more efficiently. I don't have a lot of good guidance here; we can talk in more detail later. Basically, this task involves getting to understand the library and how it works, and using it "more correctly" in Glenside. Specifically, avoiding data copies wherever possible!

[gussmith23]

@hypercubestart Please add your notes on this whenever you can! Would like to document all of the issues we had before we move on to something else.

[hypercubestart]

crossposting from #59:

on hold for now...because of difficulty of getting lifetimes to work out. Ideally, we could use ArrayViews that reference owned arrays already in the hashmap, but Rust lifetimes don't permit this

• CowArray (doesn't work because view variant has lifetimes, so if we insert array back into hashmap, we end up borrowing the hashmap mutably + immutably)
• Wrap with RC and see if that works (same error as cowarray)
• ArcArray (shared references, but same benchmarks as naive copying)
• Try out data structure idea (see whether there’s a better datatype for what we’re trying to do, better than hashmap, i.e an insert-only datastructure that guarantees that lifetimes do not change when we insert) (not quite sure if this is expressible in rust?)
• Adding a enum wrapper over ndarrray that holds owned data or views/shared data ArrayBase<MyCustomRepr…, >
• unsafe

[gussmith23]

Thanks, sorry I didn't see that comment!! Many open issues and PRs haha