Skip to content

[memory.syn] LWG 3303: ExecutionPolicy overloads of destroy/destroy_n shoudn't be constexpr #3181

Description

@frederick-vs-ja

It would be better to be consistent with other algorithms.

Activity

  1. jensmaurer commented on Aug 18, 2019

    @jensmaurer
    Member

    This sounds like an LWG issue, not an editorial one.

  2. jensmaurer commented on Oct 10, 2019

    @jensmaurer
    Member

    Submitted to lwgchair.

  3. zygoloid commented on Oct 10, 2019

    @zygoloid
    Member

    (For future reference, these functions were added by P0784R7, which specifies that they are constexpr.)

  4. Dani-Hub commented on Oct 12, 2019

    @Dani-Hub
    Member

    A corresponding LWG issue has been created: LWG 3303

  5. changed the title [-][memory.syn] ExecutionPolicy overloads of destroy/destroy_n shoudn't be constexpr[/-] [+][memory.syn] LWG 3303: ExecutionPolicy overloads of destroy/destroy_n shoudn't be constexpr[/+] on Oct 12, 2019
  6. added
    not-editorialIssue is not deemed editorial; the editorial issue is kept open for tracking.
    on Oct 12, 2019
  7. AlisdairM commented on Mar 7, 2020

    @AlisdairM
    Contributor

    Resolved by P2051R0 C++ Library Issues to be moved in Prague (Marshall Clow) cplusplus/papers#781 in Prague

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    lwgIssue must be reviewed by LWG.not-editorialIssue is not deemed editorial; the editorial issue is kept open for tracking.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions