Opening this issue to have a place to discuss what we need to to before initially putting out the code we already have. It's cool that our algorithms are already faster than what's out there so we should let others use it as soon as we can.
The minimum that needs to happen is:
Decision on what the public API looks like and what functionality we want to offer,
Documentation (with Documenter.jl? I'm not sure I've never generated documentation before),
Reorganising the package into the stable branch and then our own experimental branches.
After this we can register the package.
In terms of functionality, what do we want to make the user do? Should we have out-of-place versions of our in-place jfa! and jdac! functions?
I've not done the whole package workflow before so if you're (@goerch) comfortable with turning our repo into a package I would appreciate if you could!
Opening this issue to have a place to discuss what we need to to before initially putting out the code we already have. It's cool that our algorithms are already faster than what's out there so we should let others use it as soon as we can.
The minimum that needs to happen is:
Documenter.jl
? I'm not sure I've never generated documentation before),After this we can register the package.
In terms of functionality, what do we want to make the user do? Should we have out-of-place versions of our in-place
jfa!
andjdac!
functions?