[SparseArraysBase] Rename SparseArrayInterface
to SparseArraysBase
#1591
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed with @lkdvos offline.
SparseArrayInterface
was a bit of a misnomer since it includes both a sparse array interface, anAbstractSparseArray
supertype, and implementations ofAbstractArray
functionality. Maybe in the future we can split off the interface part into a separateSparseArrayInterface
but that is farther down the line when it is more developed.Additionally, it doesn't make much sense to keep
SparseArrayDOKs
as a separate module sinceSparseArrayInterface
/SparseArraysBase
relies heavily on theSparseArrayDOK
type as a default output type of sparse operations, and moving it intoSparseArraysBase
will make development easier. I will do that move in a future PR.