Deprecate BlockTrianglePrecondition and BlockMatrixArray. #5352
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
|
There's a merge conflict now. Can you resolve this? |
|
OK to merge once the tester is happy. |
|
/run-tests |
drwells
force-pushed
the
deprecate-block-matrix-array
branch
from
e42e810
to
0e54d05
Compare
|
that should fix things. |
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.
Closing #3733 reminded me that we still need to deprecate these two classes.
I made some small improvements to the documentation along the way: in particular, I found it hard to figure out how to set up a
BlockLinearOperatorwith multiple matrix types so I added a little example up front.