[llvm-bugs] [Bug 29000] New: std::map custom allocator with explicit copy constructor

[via llvm-bugs]

https://llvm.org/bugs/show_bug.cgi?id=29000

            Bug ID: 29000
           Summary: std::map custom allocator with explicit copy
                    constructor
           Product: libc++
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: All Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: furkanusta17 at gmail.com
                CC: llvm-bugs at lists.llvm.org, mclow.lists at gmail.com
    Classification: Unclassified

While using std::map If the custom allocator has an explicit copy constructor,
it doesn't compile.

Here is the link for the non-working code:
http://melpon.org/wandbox/permlink/wPpkYEzt0NrxTbJC

My reasoning is, in map constructor
map(const allocator_type& __a)
        : __tree_(__a)

__a is an allocator with std::pair. 

However, constructor of __tree_ expects __value_type. 
It requires copy construction which is explicit.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20160816/af2f35f6/attachment.html>