-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Closed
Labels
enhancementSomething can be improvedSomething can be improvedfixedSomething works now, yay!Something works now, yay!
Description
Over the years, we settled on a consistent pattern for SFINAE: default template arguments of the form enable_if_t<CONDITION, int> = 0. This works in a wide variety of situations, including when we have an overload set where SFINAE makes exactly one overload viable. There are a few remaining occurrences of SFINAE that don't follow this pattern.
In <hash_map>, these occurrences are:
Line 193 in 28ec9a3
| template <class _Valty, class = enable_if_t<is_constructible_v<value_type, _Valty>>> |
Line 198 in 28ec9a3
| template <class _Valty, class = enable_if_t<is_constructible_v<value_type, _Valty>>> |
Line 376 in 28ec9a3
| template <class _Valty, class = enable_if_t<is_constructible_v<value_type, _Valty>>> |
Line 381 in 28ec9a3
| template <class _Valty, class = enable_if_t<is_constructible_v<value_type, _Valty>>> |
This change is currently blocked by a compiler bug. We need to provide a reduced test case to the compiler front-end team.
(Split from #187.)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementSomething can be improvedSomething can be improvedfixedSomething works now, yay!Something works now, yay!