[specialized.algorithms] Remove typename after new #8420
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Hmm, I still think it would be cleaner to use |
Contributor
Author
|
I agree, but that seemed a much bigger change. |
The `typename` keyword is not needed to identify a dependant type in a `new` expression.
AlisdairM
force-pushed
the
remove_typename_after_new
branch
from
3a90581 to
1713b56
Compare
jwakely
approved these changes
Nov 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
The
typenamekeyword is not needed to identify a dependent type in anewexpression.This PR contributes to #3637 by resolving all current uses of
typenamein anewexpression in the library.