-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add inspector::is_trivially_nestable
.
#986
Conversation
2fe2b30
to
71c77c6
Compare
we're seeing an error now like testing locally without this commit to be sure edit: no error confirmed after popping current top two commits (including this one) |
Thanks for letting us know. I've checked the PR again, and nothing sticks out as wrong. Do you know what |
T is a which is feasibly not how it should be done, but it's what has worked until now
|
Yes! That was an interesting surprise. We still have a test for a variation using HighFive/tests/unit/test_legacy.cpp Lines 27 to 29 in 070badf
I see three options:
|
what we're doing is essentially the same as the legacy test, which I'm surprised if it's passing I can test |
oh I wasn't using |
The HighFive/include/highfive/bits/H5Slice_traits_misc.hpp Lines 268 to 279 in 070badf
The type of the pointer doesn't matter, they're all converted to |
it seems ok with |
Glad to hear that! |
This change will be documented in the Migration Guide via #996. Migration Guide: https://bluebrain.github.io/HighFive/md__2home_2runner_2work_2_high_five_2_high_five_2doc_2migration__guide.html |
We need this because
std::span
is consideredstd::is_trivially_copyable
.