-
Notifications
You must be signed in to change notification settings - Fork 15
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
Dimensions ops #38
Comments
I am happy to help if I can :) |
I think the way forward would be to move the numhask-array operations to a new project @tonyday567 What do you think if @achirkin initializes a |
Hmm, I see this project uses |
That's easier, then, we can just convert these to native dimension operations. @achirkin Does it make sense to you to maintain a separate package of idiomatic linear-algebra operations on |
I'm keen to remove the singletons dependency from here for the same reasons - just got stuck in how to best go about this. So, yes, NumHask.Array.Constraints needs to be switched to dimensions in its entirety. numhask-array is in this repo because the base library is undergoing a lot of dev, so it's easier to make changes across libraries. I'm finding that the subrepo thing works well, and happy to make a new one, or we can rip it out and make a new repo if that's easier for development purposes. |
Then I would suggest you to try using Note, I am working on branch |
unblocks: o1lo01ol1o/diffhask#8 |
Closing,, see https://github.com/tonyday567/numhask-array |
I've been working on an AD DSL based on the numhask hierarchy and array api and now that I'm filling out the numeric instances for
numhask-array
I'm finding that many type-leveldimensions
operations (transpose, tensor-product, etc) will need to be duplicated between the two packages. I propose we talk to @achirkin about making a common package of[Nat]
based operations going forward.The text was updated successfully, but these errors were encountered: