-
Notifications
You must be signed in to change notification settings - Fork 66
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
Fixing ReinterpretArray
breakage - first PR
#59
Comments
Maarten Pronk kindly pointed me to the 'fork' button in Slack. PR submitted! |
Is there anything holding up this PR? I'm getting hit by this issue in a few places. Thanks! |
The problem was if reinterpret was going to be made fast for 0.7 or if we copy the data. I guess för now we can copy and swap back to reinterpret if it gets optimized. I'll try fix up if needed and merge the PR today. |
Ok, so StaticArrays doesn't work on 0.7 so we can't really update here until that is fixed. |
Ok. |
PR merged |
The julialang PR #23750 merged last month changed the output of
reinterpret
into a lazyReinterpretArray <: AbstractArray
type. This has brokenNearestNeighbors
in a few places, where the output ofreinterpret
was expected to be of typeVector
instead. In particular the example in the README.mdfails with a
MethodError
.I have made a branch locally with a fix for this, but this being my very first PR I am posting here what I did in case I messed up.
Since
ReinterpretArray
obeys theAbstractArray
interface I just changed the signature of a number of functions expecting a::Vector{T}
into::AbstractVector{T}
. I also modified theBruteTree
constructor to ensure conversion of genericAbstractArray
s into aVector
. These changes make the README.md example work again, and they also makes it possible to once more pass tests up to a point. Tests eventually fail in relation to changes inbroadcast
, I think, but I think those failures are unrelated toReinterpretArray
. I will look into those later.I would like some tips on how to proceed to make a PR. I assume I have to push my branch and then start the PR, but I have no permissions for this. What is the standard procedure?
The text was updated successfully, but these errors were encountered: