Skip to content

type alias mfem::future::tuple to smith::tuple#1595

Merged
white238 merged 3 commits intodevelopfrom
task/white238/map_mfem_tuple_to_smith_tuple
May 6, 2026
Merged

type alias mfem::future::tuple to smith::tuple#1595
white238 merged 3 commits intodevelopfrom
task/white238/map_mfem_tuple_to_smith_tuple

Conversation

@white238
Copy link
Copy Markdown
Member

This removes a large portion of the implementation in Smith. Originally I was going to swap completely over to the mfem::tuple but it exists in a future namespace and it would have bled over all codebase. We might want to do that when it gets out of the future namespace and when we don't have large PRs up.

Copy link
Copy Markdown
Collaborator

@tupek2 tupek2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Strategy looks good to me!

* @tparam T8 The ninth type stored in the tuple
* @tparam T9 The tenth type stored in the tuple
* MFEM's tuple copy currently stores up to nine elements, while Smith's
* historical tuple API supports ten and eleven elements.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we try to add those extra two elements to the mfem tuple implementation at some point?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep

Copy link
Copy Markdown
Collaborator

@chapman39 chapman39 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems like this simplifies a lot of things and reduces duplication between mfem's implementation

Comment thread src/smith/numerics/functional/tuple_tensor_dual_functions.hpp Outdated
Comment thread src/smith/numerics/functional/boundary_integral_kernels.hpp Outdated
@white238 white238 force-pushed the task/white238/map_mfem_tuple_to_smith_tuple branch from 07bece7 to b0bf9eb Compare May 5, 2026 00:08
@white238
Copy link
Copy Markdown
Member Author

white238 commented May 5, 2026

Some of these changes can be removed after we do a bulk change to mfem's tuple, after either we move the 10,11 elements to them or to the more generic tuple I'm told might come. But this is the most minimal set of changes I could come up with w/o bleeding everywhere through the code.

@white238 white238 merged commit 0465303 into develop May 6, 2026
10 checks passed
@white238 white238 deleted the task/white238/map_mfem_tuple_to_smith_tuple branch May 6, 2026 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants