Skip to content

P0211 Allocator-aware library wrappers for dynamic allocation #323

Open
@wg21bot

Description

@wg21bot
Collaborator

P0211R2 Allocator-aware library wrappers for dynamic allocation (Thomas Köppe)

Activity

added this to the 2019-07 milestone on Jan 31, 2019
jensmaurer

jensmaurer commented on Jan 31, 2019

@jensmaurer
Member

LEWG-I in San Diego: Forward to LEWG for C++23.

modified the milestones: 2019-07, 2019-11 on Aug 23, 2019
wg21bot

wg21bot commented on Jan 18, 2020

@wg21bot
CollaboratorAuthor

P0211R3 Allocator-aware library wrappers for dynamic allocation (Thomas Köppe)

modified the milestones: 2019-11, 2020-02 on Jan 18, 2020
brycelelbach

brycelelbach commented on Feb 14, 2020

@brycelelbach

Prague 2020-02 LEWG Minutes

P0211R3 std::allocate_unique

Chair: Bryce Adelstein Lelbach

Champion: Thomas Koeppe

Minute Taker: Ben Craig

Start Review: 2020-02-13 15:52

Should allocator_new/allocator_delete use allocator_traits<>::construct/allocator_traits<>::destroy instead of placement new/destroy?

Do we want allocator_new to take a T and rebind the allocator?

Start Polling: 16:20

POLL: We must have support for arrays in allocate_unique/allocator_new/allocator_delete in the first version we ship.

Strongly For Weakly For Neutral Weakly Against Strongly Against
0 0 12 4 0

Attendance:

# of Authors: 1

Author Position: N

POLL: Users should be able to name the types of the deleters returned by allocate_unique.

Strongly For Weakly For Neutral Weakly Against Strongly Against
1 6 3 2 0

Attendance: 33

# of Authors: 1

Author Position: WF

That has weak consensus.

POLL: We must have allocate_unique_for_overwrite in the first version we ship.

Strongly For Weakly For Neutral Weakly Against Strongly Against
0 5 9 1 0

Attendance: 33

# of Authors: 1

Author Position: N

That has weak consensus.

POLL: We must support cv-qualified types in the first version of allocate_unique/allocator_new/allocator_delete.

Strongly For Weakly For Neutral Weakly Against Strongly Against
1 9 2 1 0

Attendance: 33

# of Authors: 1

Author Position: SF

That has consensus.

What allocator should allocate_unique use in the allocator_deleter:

  • The original allocator (e.g. A).
  • The rebound allocator used for allocation (e.g. A::rebind<T>).
  • The original allocator rebound to std::byte (reduces the number of allocator types you generate).
    • This breaks fancy pointer.

End: 16:53

CONSENSUS: Bring a revision of P0211R3 (allocator-aware library wrappers for dynamic allocation), with the guidance below, to LEWG for further review.

  • Array support is not required right now.
  • allocator_delete should be nameable by users.
  • Bikeshed allocator_delete on the LEWG mailing list.
  • allocate_unique/allocator_new/allocator_delete must support cv-qualified types.
  • Add allocate_unique_for_overwrite.
removed this from the 2020-02 milestone on Feb 18, 2020
added
B3 - additionBucket 3 as described by P0592: material that is not mentioned in P0592
ISShip vehicle: IS
on Aug 25, 2020

31 remaining items

Loading
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

    B3 - additionBucket 3 as described by P0592: material that is not mentioned in P0592ISShip vehicle: ISLEWGLibrary Evolutionneeds-revisionPaper needs changes before it can proceedready-for-library-evolution-meeting-reviewThis paper needs to be discussed at a Library Evolution meetingsize - smallpaper size estimate

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @brycelelbach@cor3ntin@jensmaurer@wg21bot

        Issue actions

          P0211 Allocator-aware library wrappers for dynamic allocation · Issue #323 · cplusplus/papers