This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of WP status.

3148. <concepts> should be freestanding

Section: 15.5.1.3 [compliance] Status: WP Submitter: Casey Carter Opened: 2018-08-09 Last modified: 2018-11-13

Priority: 0

View all other issues in [compliance].

View all issues with WP status.

Discussion:

The design intent of the <concepts> header is that it contains only fundamental concept definitions and implementations of customization points that are used by those concept definitions. There should never be components in the header that require operating system support. Consequently, freestanding implementations can and should provide it. It is an oversight on the part of LWG - and in particular the author of P0898R3 "Standard Libary Concepts" - that the <concepts> header is not required to be provided by freestanding implementations.

[2018-08 Batavia Monday issue prioritization]

Priority set to 0, status to 'Tentatively Ready'

[2018-11, Adopted in San Diego]

Proposed resolution:

This wording is relative to N4762.

  1. In 15.5.1.3 [compliance], add a new row to Table 21:

    Table 21 — C++ headers for freestanding implementations
    SubclauseHeader(s)
    […] […] […]
    16.12 [support.runtime] Other runtime support <cstdarg>
    17 [concepts] Concepts library <concepts>
    19.15 [meta] Type traits <type_traits>
    […] […] […]