-
-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forced C++20 requirement? #1041
Comments
While we use a This is a much bigger topic for Sentry, even though no clear boundary has yet been defined on when to fork
I fully understand this issue. Sadly, "mirroring and patching" CC: @kahest. |
User error, I am using libc++-14-dev which seem to treat its implementation of ranges as experimental until version 16 |
Unfortunately, a recent crashpad update (I believe it was 0.7.6) includes changes to mini chromium which now requires C++20 features like std::ranges. I can't see a way to conditionally make mini chromium use pre-C++20 standards.
This effectively hinders adoption and makes it impossible for a large number of projects out there to upgrade beyond sentry-native 0.7.6 as they cannot move on from C++17 yet, short of mirroring and patching mini chromium.
The text was updated successfully, but these errors were encountered: