type_index::operator<=> should not call the comparison function twice
#3600
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.
Currently, when two referenced
type_infoare not equal,type_index::operator<=>needs to call__std_type_info_comparetwice (both intype_info::operator==andtype_info::before) to determine the relative order.I think we can optimize
type_index::operator<=>by calling the comparison function at most once. However, it is currently necessary to touch the implementation details oftype_infoand__std_type_info_comparein VCRuntime. This PR is essentially mirroring the implementation of__std_type_info_comparenow.I've filed DevCom-10326599 to request a stable interface for ordering.