refactor[next]: use __gt_dims__ in LocatedField #1307
Merged
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
tehrengruber
requested changes
Aug 3, 2023
Co-authored-by: Till Ehrengruber <till.ehrengruber@cscs.ch>
tehrengruber
approved these changes
Aug 3, 2023
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.
Rename
LocatedField.axestoLocatedField.__gt_dims__to make it compatible with the Cartesian and as preparation to switch to the new field implementation.Note that gt4py.cartesian requires returning a tuple of
str, for gt4py.next we requiretuple[Dimension]. I propose to relax the cartesian requirement to convertible tostr, which should already work as the documentation demands to go throughgt4py.storage.utils.get_dims()which has string conversion.