-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FE API deprecation/changes #4077
Open
roystgnr
wants to merge
18
commits into
libMesh:devel
Choose a base branch
from
roystgnr:fe_deprecation
base: devel
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+1,460
−438
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
John added the replacements for these in 2020; it's time to ease users off the old versions.
For elements where n_dofs() depends on the specific element, we need to pass in the specific element.
The latter has to be deprecated, since without an Elem we can't make it work on polygons+polyhedra
We need to deprecate that, since it won't work on polygons+polyhedra
This should fix incompatibilities with polygons/polyhedra
And make the non-deprecated version compatible with runtime-topology elements.
Putting this in FEInterface was kind of an unintuitive decision in the first place, and now that we're adding runtime-dependent element topology like Polygons we're going to *need* a physical Elem to work with in those cases.
This should make it compatible with Polygon, etc.
This also makes one of the app options redundant
We're already beginning a big shakeup for user code so we might as well pull the bandaid off quickly.
Ripping off all the bandaids at once
libmesh_deprecated() is sometimes necessary, when one possible input is deprecated but another supported, but if *any* call to a method is deprecated we can just get rid of it completely in `--disable-deprecated` builds.
Job Coverage, step Generate coverage on 7de408a wanted to post the following: Coverage
Warnings
This comment will be updated on new commits. |
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.
As with #4076, this is a fraction of the changes in #4074, split by subsystem into its own PR for easier testing and review.