Skip to content

Conversation

@eisenwave
Copy link
Member

@eisenwave eisenwave commented Nov 16, 2025

Fixes #8478

Fixes NB AT 7-213 (C++26 CD).
Fixes NB US 140-233 (C++26 CD).
Fixes NB US 141-235 (C++26 CD).
Fixes NB US 145-234 (C++26 CD).
Fixes NB US 147-240 (C++26 CD).
Fixes NB US 164-263 (C++26 CD).
Fixes NB US 126-189 (C++26 CD).
Fixes NB US 227-346 (C++26 CD).
Fixes NB US 229-347 (C++26 CD).
Fixes NB US 221-339 (C++26 CD).
Fixes NB US 225-341 (C++26 CD).

Also fixes https://github.com/cplusplus/nbballot/issues/782
Also fixes https://github.com/cplusplus/nbballot/issues/804
Also fixes https://github.com/cplusplus/nbballot/issues/806
Also fixes https://github.com/cplusplus/nbballot/issues/805
Also fixes https://github.com/cplusplus/nbballot/issues/811
Also fixes https://github.com/cplusplus/nbballot/issues/838
Also fixes https://github.com/cplusplus/nbballot/issues/758
Also fixes https://github.com/cplusplus/nbballot/issues/921
Also fixes https://github.com/cplusplus/nbballot/issues/922
Also fixes https://github.com/cplusplus/nbballot/issues/914
Also fixes https://github.com/cplusplus/nbballot/issues/916

@eisenwave eisenwave added the changes requested Changes to the wording or approach have been requested and not yet applied. label Nov 16, 2025
Fixes NB AT 7-213 (C++26 CD).
Fixes NB US 140-233 (C++26 CD).
Fixes NB US 141-235 (C++26 CD).
Fixes NB US 145-234 (C++26 CD).
Fixes NB US 147-240 (C++26 CD).
@eisenwave eisenwave force-pushed the motions-2025-11-lwg-19 branch from f7ba14c to d402a70 Compare November 24, 2025 06:41
@eisenwave eisenwave removed the changes requested Changes to the wording or approach have been requested and not yet applied. label Nov 24, 2025
Fixes NB US 164-263 (C++26 CD).
Fixes NB US 126-189 (C++26 CD).
Fixes NB US 227-346 and US 229-347 (C++26 CD).
Fixes NB US 221-339 (C++26 CD).
Fixes NB US 225-341 (C++26 CD).
@eisenwave eisenwave force-pushed the motions-2025-11-lwg-19 branch from d402a70 to 3aebb04 Compare November 24, 2025 19:13
void @\exposid{destroy}@() noexcept; // \expos
};

template<class Alloc, @\libconcept{scope_token}@ Token, @\libconcept{sender}@ Sender, class Env> // \expos
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need the \expos comment here? It's not in the paper.

Where is this deduction guide used, only in the spec, or is its existence observable to users?

Copy link
Member Author

@eisenwave eisenwave Dec 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it may get used somehow by spawn_future; https://eel.is/c++draft/exec#spawn.future-17

Anyhow, it felt intuitively necessary, but I'm really not sure whether it actually is.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've raised it on mattermost

Copy link
Member

@jwakely jwakely left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-urgent whitespace changes, and a question about an \expos marker.

@eisenwave eisenwave requested a review from jwakely December 4, 2025 09:15
Copy link
Member

@jwakely jwakely left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

We need a decision about the \expos on the spawn-future-state deduction guide, but that doesn't need to block merging this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[2025-11 LWG Motion 19] P3923R0 Additional NB comment resolutions for Kona 2025

3 participants