session manager in memory, addressing TODO.

[devnexen]

does not seem to bring down performance.

[coveralls]

coverage: 92.062% (+0.007%) from 92.055%
when pulling 862504c on memory_manager_copy_if
into 7bc2b1c on master.

[reneme]

Given that iOS and Android were updated a while ago, perhaps we might try and get our feet wet with ranges here. Also that might actually improve readability.

[devnexen]

ok giving a try..

[devnexen]

should we update the fuzzer's toolchain too ?

[reneme]

Thanks for trying this! Could you elaborate a bit on "the issue with clang < 16", please? To me it looks like the ranges implementation simply wasn't ready for prime time, yet.

If that's true, I feel, we should just avoid range operations altogether, unfortunately. We committed to supporting Clang 14 for Botan 3.x), if it's not ready for (some) ranges features, it's just better to not use it at all, in my opinion. 😭

should we update the fuzzer's toolchain too ?

@randombit do we even have a way of doing that in OSS-Fuzz?

[devnexen]

If that's true, I feel, we should just avoid range operations altogether, unfortunately. We committed to supporting Clang 14 for Botan 3.x), if it's not ready for (some) ranges features, it's just better to not use it at all, in my opinion. 😭

Yes if you choose clang 14 as minimum I m afraid we can't indeed, clang is behind gcc, on average, in term of C++20 support.