Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Usual disclaimer about how we dislike grab-bag PRs as a general rule, and how we avoid large-scale cleanups of test code (low value, potentially disrupts the weird subtle things that the tests were trying to cover). The existence of this PR means that I think these cases are worth it for codebase consistency and that they're low-risk.
format.py
:import copy
was unused.constexpr friend
=>friend constexpr
const choose
=>choose
static
for namespace-scopepermissive()
.static
member function.filesystem_error
.P0811R3_midpoint_lerp
:static inline constexpr
=>static constexpr
inline
was accumulated before a compiler bug workaround was added.VSO_0000000_vector_algorithms
: Dropinline
aftertemplate
.inline
here.std::
qualification.std::move
andstd::forward
during an annoying era where Clang was warning about unqualified calls before we silenced that; I don't think it's worth the effort to go clean them up.P0083R3_splicing_maps_and_sets
:#ifdef __cpp_constinit
=>#if _HAS_CXX20