-
Notifications
You must be signed in to change notification settings - Fork 269
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
Use the C++17 standard [[nodiscard]]
attribute directly
#8036
Use the C++17 standard [[nodiscard]]
attribute directly
#8036
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #8036 +/- ##
========================================
Coverage 79.09% 79.09%
========================================
Files 1699 1699
Lines 196508 196508
========================================
Hits 155430 155430
Misses 41078 41078 ☔ View full report in Codecov by Sentry. |
As we now require `C++17` support, the `[[nodiscard]]` attribute is required to be supported across all platforms.
This makes it more straight forward for new maintainers with pre-existing C++17 knowledge to read our code base without learning `NODISCARD`, which is specific to our codebase.
Because it is no longer needed.
8cfac64
to
0857208
Compare
I'd like to check how nodiscard issues are reported across each of the platforms we support, before I move this PR out of draft and merge it. I have raised #8038 for this purpose. |
Looks like the error/warning reporting is the same before and after this PR. Therefore I am now happy for this to be merged. |
As we now require
C++17
support, the[[nodiscard]]
attribute should be required to be supported across all platforms. Using it directly makes it more straight forward for new maintainers with pre-existing C++17 knowledge to read our code base without learningNODISCARD
, which is specific to our codebase.