Make append! and push! definitions more generic #32065
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some methods for
append!
andpush!
forArray
actually work for anyAbstractArray
since they only useresize!
,setindex!
andpush!
. Broaden the signatures so that custom array types do not need to copy definitions from Base.BitArray
uses special methods, one of which was apparently not covered by tests.Ideally, fallback
append!(::AbstractVector, ::AbstractVector)
andpush!(::AbstractVector, ::Any)
methods would also be provided. Unfortunately, the existing definitions forVector
call_grow_end
instead ofresize!
, which means that simply broadening the signature toAbstractVector
won't work. It would be easy to fix that (usingx isa Vector
or a helper function), but since the non-Vector
code path would not be used in Base I'm not sure that's OK. Comments?