Replace type unstable tuple call with type-stable ntuple call #3471
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
glwagner
reviewed
Feb 12, 2024
Made suggested edits to variable names for clarity Co-authored-by: Gregory L. Wagner <wagner.greg@gmail.com>
:q q end
glwagner
changed the title
…icFreeSurfaceModels.top_tracer_boundary_conditions
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.
Just replaced the tuple line in
permute_boundary_conditions(in filesrc/BoundaryConditionsfill_halo_regions.jl) with an ntuple call that makes it type-stable and eases use of Enzyme.