Always use similar as fallback when resize throws in applying composite maps #221
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.
When using subtypes of
AbstractVector
that do not supportresize!
(such asBlockArrays.PseudoBlockVector
), the memory optimisation in the_unsafe_mul!
for composite maps result in errors.I have changed
_resize
to allways fall back to memory allocation viasimilar
, whereas previously this only happened when the argument was aSharedArrays.SharedVector
.