Movatterモバイル変換


[0]ホーム

URL:



This page is a snapshot from the LWG issues list, see theLibrary Active Issues List for more information and the meaning ofC++14 status.

2050. Unordered associative containers do not useallocator_traits to define member types

Section: 23.5[unord]Status:C++14Submitter: Tom ZiebermanOpened: 2011-04-29Last modified: 2016-01-28

Priority:Not Prioritized

View all otherissues in [unord].

View all issues withC++14 status.

Discussion:

The unordered associative containers define their member typesreference,const_reference,pointer,const_pointer in terms of their template parameterAllocator (viaallocator_type typedef). As a consequence, only the allocator types, that provide sufficient typedefs, are usable as allocators for unordered associative containers, while other containers do not have this deficiency. In addition to that, the definitions of said typedefs are different from ones used in the other containers. This is counterintuitive and introduces a certain level of confusion. These issues can be fixed by definingpointer andconst_pointer typedefs in terms ofallocator_traits<Allocator> and by definingreference andconst_reference in terms ofvalue_type as is done in the other containers.

[2011 Bloomington.]

Move to Ready.

Proposed resolution:

This wording is relative to the FDIS.


[8]ページ先頭

©2009-2026 Movatter.jp