You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been realizing that the intent behind most "data classes" is to have no/very few methods on them, as they're intended to act like "records".
It would be interesting to experiment with making the DP classes into "records"?
Alternately, another idea might be to move from subclassing Rule > Solution > Result, to having a (say) CourseRule record, which is attached to a CourseSolution record, which is attached to a CourseResult record?
So instead of having to copy all of the properties, and subclassing as we do now, we could just essentially stick a pointer into it.
I've been realizing that the intent behind most "data classes" is to have no/very few methods on them, as they're intended to act like "records".
It would be interesting to experiment with making the DP classes into "records"?
Alternately, another idea might be to move from subclassing Rule > Solution > Result, to having a (say) CourseRule record, which is attached to a CourseSolution record, which is attached to a CourseResult record?
So instead of having to copy all of the properties, and subclassing as we do now, we could just essentially stick a pointer into it.
Something like
Hmm. Something like that.
The text was updated successfully, but these errors were encountered: