AbstractVecOrMat, not StridedVecOrMat, in tridiagonal methods #32147
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looks like the buildbots are displeased due to the inevitable method ambiguities? Best! |
|
Grr, yes, this requires more work. |
|
StefanKarpinski
added
the
help wanted
|
Since the original motivation for this PR disappeared, we may as well close it. The allocations were, most likely, due to the generation of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It looks like several of the methods for tridiagonal methods were unnecessarily restricted to act on
StridedVecOrMatrather thanAbstractVecOrMat.I noticed this because someone reported that
mul!with a view was still allocating lots of memory (https://discourse.julialang.org/t/symtrididiagonal-matrices-performance-and-views-allocations)