Skip to content

STL: !_HAS_EXACT_COMPOUND_REQUIREMENT fallbacks are unnecessary #299

@CaseyCarter

Description

@CaseyCarter

Many of the concept definitions in the standard library have two definitions conditional on _HAS_EXACT_COMPOUND_REQUIREMENT. The intent is to be able to support both conforming implementations of C++20 concepts and clang-concepts, which until quite recently had not implemented WG21-P1084's change to return-type-requirements. I've verified with the author of clang-concepts that clang proper will certainly support P1084's semantics when it defines __cpp_concepts, so we can remove _HAS_EXACT_COMPOUND_REQUIREMENT from the STL as well as all conditional code that is used when _HAS_EXACT_COMPOUND_REQUIREMENT is 0.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementSomething can be improvedfixedSomething works now, yay!good first issueGood for newcomers

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions