-
Notifications
You must be signed in to change notification settings - Fork 37
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
ismutable wrong for FillArrays #77
Comments
I like the idea of mutability being something that needs to be opted into. I didn't originally make Does this break anything. |
How many libraries are currently using Barring breaking a bunch of stuff, I think it's okay to make |
basically anything that is mutable will eventually |
Should we suggest using |
No, |
I assume all AbstractFill are immutable? If that's true, we should just make an extension library for FillArrays that does that. I'll wait until someone who knows FillArrays.jl better responds and makes sure that's true. |
FillArrays are not mutable.
I think that
https://github.com/SciML/ArrayInterface.jl/blob/730592e19c5e3effb086a5cc0b61ecc1a1936a76/src/ArrayInterface.jl#L75-L81
Should be
Alternatively
the fallback case could be:
return T.mutable
rather thanfalse
.On the assumption that if you are a mutable struct that has subtypes
AbstractArray
you probably have definedsetindex
The text was updated successfully, but these errors were encountered: