Configure build for span implementation

[thompsonbry]

At some point span is part of c++ and we should adapt the build to that. It leaks through the API since the value_view (and soon the key) will be spans. So it is unfortunate that we do not have a stable type here. A configurable using declaration and include for the build might help with that.

[laurynas-biveinis]

GCC 10 and clang 11 - the oldest supported compilers - both have std::span. Do you think there would be any issues in just switching?

The remaining GSL feature used would be narrow_cast, and I'm OK with reimplementing or even dropping it

[laurynas-biveinis]

The issue with my suggestion above is that we can't selectively enable C++20 library features while the library remains C++17

[laurynas-biveinis]

@thompsonbry, would there be a problem if the library switched to C++20 to the extent GCC 10 supports it already?

[thompsonbry]

That would be fine. We are using 10.5.0

…

On Mon, Jan 13, 2025 at 7:38 AM Laurynas Biveinis ***@***.***> wrote: @thompsonbry <https://github.com/thompsonbry>, would there be a problem if the library switched to C++20 to the extent GCC 10 supports it already? — Reply to this email directly, view it on GitHub <#634 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AATW7YETYWJTEJZIEZMEDZT2KPMVPAVCNFSM6AAAAABVCROVU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBXGQ2TONZUGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[thompsonbry]

Should this issue be closed?

[laurynas-biveinis]

I think we can close it once we actually have tests for span-based keys