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

[SparseArraysBase] Rename SparseArrayInterface to SparseArraysBase #1591

Merged
merged 1 commit into from
Nov 16, 2024

Conversation

mtfishman
Copy link
Member

@mtfishman mtfishman commented Nov 15, 2024

As discussed with @lkdvos offline. SparseArrayInterface was a bit of a misnomer since it includes both a sparse array interface, an AbstractSparseArray supertype, and implementations of AbstractArray functionality. Maybe in the future we can split off the interface part into a separate SparseArrayInterface 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 since SparseArrayInterface/SparseArraysBase relies heavily on the SparseArrayDOK type as a default output type of sparse operations, and moving it into SparseArraysBase will make development easier. I will do that move in a future PR.

@mtfishman mtfishman changed the title [WIP] [SparseArraysBase] Rename SparseArrayInterface to SparseArraysBase, absorb SparseArrayDOKs [SparseArraysBase] Rename SparseArrayInterface to SparseArraysBase Nov 15, 2024
@mtfishman mtfishman marked this pull request as ready for review November 15, 2024 23:11
@mtfishman mtfishman merged commit 9ef8ae2 into main Nov 16, 2024
13 checks passed
@mtfishman mtfishman deleted the SparseArraysBase branch November 16, 2024 00:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant