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
rhornung67 opened this issue
Aug 15, 2024
· 4 comments
· Fixed by #1443
Assignees
Labels
CoreIssues related to Axom's 'core' componentdesignIssues related to design and software engineeringReviewedSidreIssues related to Axom's 'sidre' component
Since those classes are not specific to Axom and have no other Axom dependencies, it makes sense to move them to the Axom core component.
The text was updated successfully, but these errors were encountered:
rhornung67
added
Core
Issues related to Axom's 'core' component
Sidre
Issues related to Axom's 'sidre' component
design
Issues related to design and software engineering
labels
Aug 15, 2024
The one Axom dependency that exists in these collection classes is slic, as there are a few assertions and one warning. Removing them would have no effect on the functionality, but would increase risk in the case that calls are made that would have triggered the assertions or warning. Is there a reasonable alternative to slic in this case?
Thanks @bmhan12, I can definitely do that for the assertions. For the warning, I suppose I should write a std::cerr message like in axom::Array since I don't have access to the Logger.
CoreIssues related to Axom's 'core' componentdesignIssues related to design and software engineeringReviewedSidreIssues related to Axom's 'sidre' component
Sidre's map and item collections can be used in other components:
Since those classes are not specific to Axom and have no other Axom dependencies, it makes sense to move them to the Axom core component.
The text was updated successfully, but these errors were encountered: