-
Notifications
You must be signed in to change notification settings - Fork 150
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
ambiguity generated by default copyto!
method
#1097
Comments
I don't understand, what exactly is the problem with this method? What is
There would very likely be a performance regression, you'd have to benchmark a few statically sized broadcasts to verify that. |
In general,
at least in the coverage, that method isn't touched, because there is also: StaticArrays.jl/src/broadcast.jl Line 66 in 17e8c37
that catches all x<:AbstractArray uses of copyto! and it's the one that is actually used
|
I see now, that's actually a good point -- I agree, removing that methods looks like a good idea. |
Fixed by #1098 . |
this line:
StaticArrays.jl/src/broadcast.jl
Line 65 in 17e8c37
seems that _copyto! only special handles methods that have static axes. is is correct to assume that those axes only happen on
x <: AbstractArray
?. if that is the case, then other type trying to dispatch oncopyto!
only needs to define:then, if an external package needs to define
but the catchall method causes ambiguities in that regard.
I did a test run of StaticArrays on julia 1.8/windows, and removed that method. all tests passed.
The text was updated successfully, but these errors were encountered: