Issue 4063: Freestanding std::char_traits<char>::eof depends on non-freestanding EOF

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

4063. Freestanding `std::char_traits<char>::eof` depends on non-freestanding `EOF`

Section: 23.2.4.2 [char.traits.specializations.char] Status: New Submitter: Jiang An Opened: 2024-04-03 Last modified: 2024-04-05

Priority: Not Prioritized

View all other issues in [char.traits.specializations.char].

View all issues with New status.

Discussion:

Currently EOF is not yet freestanding, because it's only specified to be provided in <stdio.h> in C, or together with <cstdio> in C++.

However, std::char_traits<char>::eof (required to be freestanding since C++26 by P2338R4) is required to return the value of EOF. It's unclear what is expected to be done in a freestanding implementation.

Related to LLVM issue #85158.

Proposed resolution:

4063. Freestanding std::char_traits<char>::eof depends on non-freestanding EOF

4063. Freestanding `std::char_traits<char>::eof` depends on non-freestanding `EOF`