You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 4, 2019. It is now read-only.
Okay, that's undefined behavior. But I can imagine the following (or something like it) biting somebody trying to do something reasonable:
julia> A = [1:10...];
julia> X =NullableArray(A);
julia>splice!(A, 1)
1
julia> X
9-element NullableArrays.NullableArray{Int64,1}:Nullable(2)
Nullable(3)
Nullable(4)
Nullable(5)
Nullable(6)
Nullable(7)
Nullable(8)
Nullable(9)
Nullable(10)
julia> X.isnull
10-element Array{Bool,1}:falsefalsefalsefalsefalsefalsefalsefalsefalsefalse
Thoughts? Really it shouldn't be unexpected since Julia passes by reference, but I'm wondering if there's anything we ought to do to make it more obvious that you might have broken something. Then again, the best (and maybe only feasible) thing to do may just be to include a caveat in the documentation.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Okay, that's undefined behavior. But I can imagine the following (or something like it) biting somebody trying to do something reasonable:
Thoughts? Really it shouldn't be unexpected since Julia passes by reference, but I'm wondering if there's anything we ought to do to make it more obvious that you might have broken something. Then again, the best (and maybe only feasible) thing to do may just be to include a caveat in the documentation.
The text was updated successfully, but these errors were encountered: