-
Notifications
You must be signed in to change notification settings - Fork 102
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
Errors are ugly when trying to write to a const buffer #931
Comments
Strange, I tested with Clang 18, but I'll have to set up an environment to test with Clang 19. The behavior seems strange. Can you try using the latest release (v2.5.2)? Because the main branch has some #include refactoring associated with |
I was using the main branch at commit cdd097a Using the tag 2.5.2 with hash 4749325 also yields errors:
|
I would be surprised if Clang 19 introduced significant compiler bugs. It's probably something wrong with your setup. I'll build a dev container with Clang 19 to test. But, the code builds with Clang 15,16,17, and 18 |
Clang 19 works on compiler explorer: https://gcc.godbolt.org/z/WzzshzffM |
Well, testing with clang 19 it does not compile using write-Method with prettier: https://gcc.godbolt.org/z/9d4M1Yh1f |
Oh, thank you! Will fix ASAP. |
The issue is actually not a bug, but that you're trying to write to a This does indicate that we need much better error messages when someone tries to write to a const qualified buffer. I'll keep this issue open until that is resolved. |
Better erroring when trying to write to a const buffer has been added. Thanks for bringing this up! |
Another issue arised:
I'm trying to get the example working:
I've deactivated clang-tidy and using clang++ version 19 now.
The errorlog is as follows:
I attached the rest of the log file.
error.log
This error occurs using the
write<>
Method with allstring_literals
within dump.hppThe text was updated successfully, but these errors were encountered: