Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

P2407R5 Freestanding Library: Partial Classes #4172

Closed
StephanTLavavej opened this issue Nov 12, 2023 · 1 comment · Fixed by #4743
Closed

P2407R5 Freestanding Library: Partial Classes #4172

StephanTLavavej opened this issue Nov 12, 2023 · 1 comment · Fixed by #4743
Labels
cxx26 C++26 feature fixed Something works now, yay!

Comments

@StephanTLavavej
Copy link
Member

StephanTLavavej commented Nov 12, 2023

WG21-P2407R5 Freestanding Library: Partial Classes

Feature-test macros (expected):

#define __cpp_lib_freestanding_algorithm   202311L
#define __cpp_lib_freestanding_array       202311L
#define __cpp_lib_freestanding_optional    202311L
#define __cpp_lib_freestanding_string_view 202311L
#define __cpp_lib_freestanding_variant     202311L

We're not entirely sure what our hosted implementation needs to do here. IF the only thing that we need to do is define these feature-test macros, then we'll accept a PR for this (like #3837) before we open up the floodgates to arbitrary C++26 features.

@CaseyCarter
Copy link
Contributor

I'm now entirely sure. P2407R5 adds wording "On freestanding implementations, it is implementation-defined whether each entity introduced by a freestanding-deleted function is a deleted function ([dcl.fct.def.delete]) or whether the requirements are the same as the corresponding requirements for a hosted implementation." Our hosted implementation trivially conforms since it implements the entities as specified.

TLDR: we only need define the new feature-test macros.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cxx26 C++26 feature fixed Something works now, yay!
Projects
Development

Successfully merging a pull request may close this issue.

2 participants