C++17 support

[nullsysvoid]

Hi! I would like to use this library with embedded device but it uses arm gcc compiler with C++17 support and there is no any plans to move to new C++20 standard. So I would like to know if you have any plans to use C++17 in this project? I looked at the code and in general only concepts and format are used from the new standard.

[nullsysvoid]

Thank you

[nullsysvoid]

Also
Macros do not have to be used inside the source code, you can make 2 implementations and link them depending on the standard in cmake. This will make the code clean from conditional compilations

[Curve]

Also
Macros do not have to be used inside the source code, you can make 2 implementations and link them depending on the standard in cmake. This will make the code clean from conditional compilations

This is what I do in all of my other projects but this is not true for header files, where the most C++20 features are used currently.

Sure we could have conditional includes but that just makes everything unnecessarily cluttered.

[nullsysvoid]

This can also be solved, for example, instead of using fmt directly, you can use a wrapper class over it

[Curve]

This can also be solved, for example, instead of using fmt directly, you can use a wrapper class over it

Format is not used in the headers but concepts, which are a language feature...

Also, due to the template heavy nature of format a non-header heavy approach is not plausible

[Curve]

Okay, I've just looked into this - And back-porting the current code-base is a lot more work than I initially anticipated due to some of the dependencies also relying on C++20.

I don't think it's currently in scope to add C++17 support back in completely.
However using Rohrkabel v1.5 should work fine since most updates since then have mostly been QoL changes.

[nullsysvoid]

Thank you for response. I will try to check with ver.1.5