refactor: split FieldSpecificationBase into two classes#4025
Open
refactor: split FieldSpecificationBase into two classes#4025
Conversation
kdrienCG
requested review from
bd713,
castelletto1,
cssherman,
frankfeifan,
jhuang2601,
kimtaeho07 and
tjb-ltk
as code owners
kdrienCG
removed
the
ci: run integrated tests
kdrienCG
added
ci: run CUDA builds
MelReyCG
reviewed
Apr 13, 2026
kdrienCG
removed
ci: run CUDA builds
MelReyCG
reviewed
Apr 15, 2026
The affected part may need a larger refactor to generalize logging on field application.
(when appropriate)
MelReyCG
approved these changes
Apr 16, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
(Previously #4011)
This PR aims to refactor the FieldSpecificationBase class into two separate class.
FieldSpecificationfor the data.FieldSpecificationImplfor the "behavior" (with methods likeapply,computeRhsContribution, etc.).This will separate concerns and make the code easier to understand when encountering field specifications.
The following architecture is proposed: