Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider using a tensor lib for native memory (instead of flat slices) #20

Open
jonysy opened this issue Mar 4, 2017 · 1 comment
Open

Comments

@jonysy
Copy link
Owner

jonysy commented Mar 4, 2017

@jonysy
Copy link
Owner Author

jonysy commented Mar 5, 2017

alexandermorozov:

ndarray solves first part by accepting constant values, slices, Vecs and iterators as initializers. But it doesn't allow to allocate uninitialized chunk of memory to be overwritten later; looks like there is no way to statically check if usage is correct, so checks have to be done at runtime and that'll have a small runtime cost.

jonysy added a commit that referenced this issue Mar 16, 2017
* This closes #2 and closes #18
* I kept running into issues w/ the libloading crate (referencing #15)
* I'm currently playing around with NDArray (referencing #20), though
the way the Index trait works with ArrayBase is rather complicated
* See the changelog for more information
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant