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
working through fixing some rcField tests as I merge sandialabs. I'm wondering if there is any reason why we shouldn't push all of the rcField functions to be private methods on the mesh class? If I understand correctly these functions are all there to have an internal cache of stored values of the reverse classification.
If this is correct, then we should make all those methods private and just have the ask_revClass etc. functions be exposed in the namespace.
The text was updated successfully, but these errors were encountered:
I can make this change when I'm done doing the merge with sandialabs. I will submit a pull request and request your approval to make sure I'm not too zealous with hiding things.
working through fixing some rcField tests as I merge sandialabs. I'm wondering if there is any reason why we shouldn't push all of the rcField functions to be private methods on the mesh class? If I understand correctly these functions are all there to have an internal cache of stored values of the reverse classification.
If this is correct, then we should make all those methods private and just have the
ask_revClass
etc. functions be exposed in the namespace.The text was updated successfully, but these errors were encountered: