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

LWG Poll 2: P2051R0 C++ Standard Library Issues to be moved in Prague #3748

Merged
merged 44 commits into from Feb 27, 2020

Conversation

@jensmaurer jensmaurer added this to the post-2020-02 milestone Feb 19, 2020
@jensmaurer jensmaurer changed the title Motions 2020 02 lwg 2 P2051R0 C++ Standard Library Issues to be moved in Prague Feb 19, 2020
@jwakely
Copy link
Member

jwakely commented Feb 19, 2020

Is everything in this branch also in motions-2020-02-lwg-3 ?

source/containers.tex Outdated Show resolved Hide resolved
source/containers.tex Show resolved Hide resolved
source/time.tex Outdated Show resolved Hide resolved
source/utilities.tex Outdated Show resolved Hide resolved
@JohelEGP
Copy link
Contributor

Is everything in this branch also in motions-2020-02-lwg-3 ?

Here's a diff: https://github.com/cplusplus/draft/compare/db3a6049bd7ae1244d0c6a09cfd3ea4b69cdf452..ea509911557a236702dccba48f2d2a2fa55322d0.

Copy link
Member

@jensmaurer jensmaurer left a comment

Choose a reason for hiding this comment

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

Please augment each commit description with a "Also fixes NB US xxx (C++20 CD)." where applicable.

For example, LWG3319 fixes DE 344.
This is recorded in the source paper as "Addresses DE 344".

This is probably a situation where a force-push is desirable, despite these being straw-polls papers.

@jensmaurer jensmaurer added the changes requested Changes to the wording or approach have been requested and not yet applied. label Feb 21, 2020
@jensmaurer
Copy link
Member

jensmaurer commented Feb 21, 2020

LWG 3280 also fixes US 302, but is not marked as such.
LWG 3286 also fixes US 304, but is not marked as such.
LWG 3284 also fixes US 262, but is not marked as such.
LWG 3304 also fixes US 217, but is not marked as such.
LWG 3292 also fixes US 286, but is not marked as such.

@jensmaurer jensmaurer changed the title P2051R0 C++ Standard Library Issues to be moved in Prague LWG Poll 2: P2051R0 C++ Standard Library Issues to be moved in Prague Feb 21, 2020
@burblebee
Copy link
Contributor Author

Is everything in this branch also in motions-2020-02-lwg-3 ?

Yes, lwg-3 was based on lwg-2 in order to resolve conflicts where issues from both motions changed the same wording.

@jensmaurer
Copy link
Member

jensmaurer commented Feb 21, 2020

LWG 3281 also fixes US 284, but is not marked as such.
LWG 3285 also fixes US 156, but is not marked as such.
LWG 3291 also fixes US 287, but is not marked as such.

@burblebee
Copy link
Contributor Author

LWG 3280 also fixes US 302, but is not marked as such.
....

Thanks for pointing these out! Done - please recheck.

@burblebee burblebee removed the changes requested Changes to the wording or approach have been requested and not yet applied. label Feb 21, 2020
@burblebee
Copy link
Contributor Author

LWG 3280 also fixes US 302, but is not marked as such.
....

Thanks for pointing these out! Done - please recheck.

Ugh - I did force push as Jens suggested, but that was probably a mistake - it will screw things up for @zygoloid when he tries to merge motions-2020-02-lwg-3 which was based on this :(.
@zygoloid, should I force-push motions-2020-02-lwg-3 also?

source/utilities.tex Outdated Show resolved Hide resolved
@burblebee
Copy link
Contributor Author

LWG 3280 also fixes US 302, but is not marked as such.
....

Thanks for pointing these out! Done - please recheck.

Ugh - I did force push as Jens suggested, but that was probably a mistake - it will screw things up for @zygoloid when he tries to merge motions-2020-02-lwg-3 which was based on this :(.
@zygoloid, should I force-push motions-2020-02-lwg-3 also?

I'm going to go ahead and force push motions-2020-02-lwg-3 rebased on motions-2020-02-lwg-2, hope that's OK.

@JohelEGP
Copy link
Contributor

The force-pushed link shows that one of the changes was lost.

@burblebee
Copy link
Contributor Author

burblebee commented Feb 25, 2020

The force-pushed link shows that one of the changes was lost.

@JohelEGP The change from \exposid{iterator}::iterator_concept back to \exposid{iterator}::iterator_concept in [range.filter.iterator]/p2 was intentional, as that line was not changed by this motion (it was added in Nov. 2018 for P0896R4). There are several remaining iterators that should be should be \exposid{iterator}ed, but as a separate edit issue.

@JohelEGP
Copy link
Contributor

@burblebee
Copy link
Contributor Author

The force-pushed link shows that one of the changes was lost.

Oh? Which one?

https://github.com/cplusplus/draft/compare/46b038136e41f02ddeac66882ff53c5dff42a849..4185912a94c33ca909de86b59e0167b48a00b095#diff-0754a9e20af4b80758260aaad60a4d1eL3100

That was intentional, see my modified comment above (I guess we added comments here at the same time :) )

Dawn Perchik added 27 commits February 26, 2020 17:40
Also fixes NB JP 218, JP 219 (C++20 CD).
Also fixes NB US 162, US 163 (C++20 CD).
[time.duration.io] Combined paragraphs 3 and 4 with 2 (now 1)
to provide a complete definition for the placeholder "units_suffix"
introduced in the code in paragraph 2, and added punctuation.

Also fixes NB US 334 (C++20 CD).
Also fixes NB DE 344 (C++20 CD).

[Bibliography] Changed punctuation to be consistent with existing entries.
…:[ranges::]cbegin/cend

Also fixes NB PL 247 (C++20 CD).
[range.split.outer.value] The change to split_view was applied in LWG3276.

Also fixes NB DE 282 (C++20 CD).
…mmon_reference_with

Also fixes NB US 201 (C++20 CD).
Added references to header synopsis on #includes.

Also fixes NB US 181 (C++20 CD).
parameter to allow idiomatic use of std::forward.
@zygoloid zygoloid merged commit 68f753c into master Feb 27, 2020
@jensmaurer jensmaurer deleted the motions-2020-02-lwg-2 branch February 12, 2021 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment