Cleanups: Avoid almost always auto
#3530
Merged
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.
We conventionally avoid the pattern
auto variable = Type{args};
because it is strictly more complicated thanType variable{args};
. Following this convention reservesauto
for the cases where it's doing real work to deduce a type.We've accumulated a few cases which I'm cleaning up here. (There are a few more cases which I am reluctantly not changing, because
auto
results in code lining up nicely. I thought about it, though.)In
P2321R2_views_zip
, I'm also performing some renames. We can name the parameterssingle_element_container
andthree_element_container
, as that's relevant to the caller. Then we can rename the local copy to justwritable
, which avoids wrapping lines.In
<__msvc_int128.hpp>
, I'm usingstatic_cast
. MSVC emits a signed/unsigned warning if we attempt to directly initialize_Int_max
(possibly becausenumeric_limits::max()
isconstexpr
but notconsteval
). Since we're intentionally changing the type fromint
tosize_t
, it seems stylistically best to emphasize this with astatic_cast
anyways.