Add a status page for P2321R2
Details
- Reviewers
• Quuxplusone ldionne Mordante - Group Reviewers
Restricted Project - Commits
- rGd5b5fc06b85a: [libc++] Add Status page for P2321R2 (Zip)
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
libcxx/docs/Status/Zip.rst | ||
---|---|---|
18 | s/imperitave/imperative |
LGTM % comments... although this would be another place we could try using GitHub issues instead of .csv files, if we wanted to. (I'm neutral.)
libcxx/docs/Status/Zip.rst | ||
---|---|---|
18–20 | I'd just replace this whole sentence with This avoids duplicating effort. libc++ is hardly known for "effective implementation," ;) and I don't actually see how this has any effect on "implementors [getting] blocked by each other." In a sense, having this list (a synchronization mechanism) is what makes it possible for one person to get blocked by another; without it, you'd just duplicate the other person's work (which could lead to starvation of the slower worker, but never deadlock). | |
24 |
- Added enable_borrowed_range zip_view and adjacent_view task
libcxx/docs/Status/ZipProjects.csv | ||
---|---|---|
7 | All these weird line breaks are forced line breaks in the generated table. I'm not exactly fluent in Sphinx, but I don't think there is a better way. At least it's done the same way in SpaceshipProjects.csv. |
The CI for the documentation has been enabled again, can you rebase this commit to see whether the CI is happy?
libcxx/docs/Status/ZipProjects.csv | ||
---|---|---|
7 | I see I hadn't noticed that in spaceship before. |
Nevermind. It seems when you select https://reviews.llvm.org/D116691/new/ you sometimes get unrelated changes :-(
I also noticed I'm the second reviewer.
s/imperitave/imperative