Closed antonysigma closed 1 year ago
Of course we can include C++20 code BUT it has to be protected, because HighFive is still compliant C++11.
Since the above nicely decays to less modern C++ in a manner that works well for both older compilers and buggy compilers. I can see how this makes users life easier since it's plausible they'd need to implement Properties for properties we don't support (yet). I think we can add something like this.
For sure. I will submit a draft PR for the PropertyInterface
concept. To test the reaction from Highfive developers.
Update: @1uc @alkino . Here you are: https://github.com/BlueBrain/HighFive/pull/811
I like the meta-programming feature built into the HighFive library. Thank you!
I am wondering if I can contribute C++20 code to make the compiler error more readable for average users?
For example, I want the compiler to report the missing
struct Deflate::apply()
function directly, instead of printing 100+ lines ~to~ of failed recursive template instantiations.Here's the example C++20 concepts code: