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
It's convenient to have the option of telling HighFive to just write from a pointer. Currently, one does this with:
dset.read(ptr);
dset.write_raw(ptr);
We should unify the two. Potentially, important twist to consider are things like std::string* which points to a pre-allocated array of strings. Which can't be used in *_raw because it'll segfault. However, it would make sense for read(ptr) and write(ptr) to use the pre-allocated array of std::strings and then copy the strings into/from the pre-allocated array from/to an internal buffer used to read/write the strings.
The text was updated successfully, but these errors were encountered:
1uc
added
the
v3
Anything that needs to be resolved before `v3`.
label
Nov 27, 2023
It's convenient to have the option of telling HighFive to just write from a pointer. Currently, one does this with:
We should unify the two. Potentially, important twist to consider are things like
std::string*
which points to a pre-allocated array of strings. Which can't be used in*_raw
because it'll segfault. However, it would make sense forread(ptr)
andwrite(ptr)
to use the pre-allocated array ofstd::string
s and then copy the strings into/from the pre-allocated array from/to an internal buffer used to read/write the strings.The text was updated successfully, but these errors were encountered: