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

Meta LWG issue: 2024-06 meeting #4759

Closed
13 tasks done
StephanTLavavej opened this issue Jun 30, 2024 · 0 comments
Closed
13 tasks done

Meta LWG issue: 2024-06 meeting #4759

StephanTLavavej opened this issue Jun 30, 2024 · 0 comments
Labels
LWG Library Working Group issue meta Issues about issues! resolved Successfully resolved without a commit

Comments

@StephanTLavavej
Copy link
Member

StephanTLavavej commented Jun 30, 2024

(Previous meta-issue: #4491)

At the June 2024 meeting, the following LWG issues were resolved in the C++ Working Paper.

❔ Not yet analyzed

  • Remaining issues:
    • All done!

❌ Not applicable

If an issue requires no action from implementers, we mark it as N/A. Categories:

  • Pure wording clarifications with nothing to implement (these can be changes to non-normative text like examples and informative notes, or wording cleanups to normative text that don't impact observable behavior)
    • LWG-4076 concat_view should be freestanding
  • Something that increases the restrictions placed on users, but implementers aren't expected to enforce those restrictions
  • Fixes for obviously broken wording, where implementers would have done the right thing anyways

😸 Already implemented

Sometimes we cite LWG issues in product code comments as we're implementing their proposed resolutions. When the resolutions are officially accepted, we should remove the citations (as the default assumption is that we're implementing what the Standard says). If something is especially subtle, we can convert the citation to mention the relevant Standard section. Sometimes we should add test coverage - e.g. when the Standard begins requiring something that we were already doing, but weren't explicitly testing for.

  • Already implemented, comments need to be removed and messages need to cite the Standard
  • Implemented without comments

🩹 Patches an unimplemented feature

We should record this LWG issue in the GitHub issue tracking the feature. That way, we'll remember to verify it, but it doesn't represent net new work.

🐞 Not yet implemented

@StephanTLavavej StephanTLavavej added LWG Library Working Group issue meta Issues about issues! labels Jun 30, 2024
@github-project-automation github-project-automation bot moved this to Available in STL LWG Issues Jun 30, 2024
@StephanTLavavej StephanTLavavej added the resolved Successfully resolved without a commit label Jun 30, 2024
@github-project-automation github-project-automation bot moved this from Available to Done in STL LWG Issues Jun 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LWG Library Working Group issue meta Issues about issues! resolved Successfully resolved without a commit
Projects
Status: Done
Development

No branches or pull requests

1 participant