Skip to content

Meta LWG issue: 2022-07 meeting #2872

Closed

Description

(Previous meta-issue: #2527)

At the July 2022 virtual plenary meeting, the resolutions of the following LWG issues were merged into the C++ Working Paper.

❔ Not yet analyzed

❌ 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-3659 Consider ATOMIC_FLAG_INIT undeprecation
      • MSVC STL has never deprecated this macro, and it might be impossible to reflect such deprecation in a library implementation
  • 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
    • LWG-3670 Cpp17InputIterators don't have integer-class difference types
    • LWG-3705 Hashability shouldn't depend on basic_string's allocator
  • Implemented without comments
    • LWG-3687expected<cv void, E> move constructor should move
    • LWG-3703 Missing requirements for expected<T, E> requires is_void<T>
    • LWG-3704 LWG-2059 added overloads that might be ill-formed for sets
    • LWG-3708 take_while_view::sentinel's conversion constructor should move

🩹 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.

  • LWG-3692 zip_view::iterator's operator<=> is overconstrained
  • LWG-3702 Should zip_transform_view::iterator remove operator<?

🐞 Not yet implemented

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

Metadata

Assignees

No one assigned

    Labels

    LWGLibrary Working Group issuemetaIssues about issues!resolvedSuccessfully resolved without a commit

    Type

    No type

    Projects

    • Status

      Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

        翻译: