[llvm-bugs] [Bug 43764] New: Unqualified name use causes ambiguity through ADL (forward_as_tuple)

[via llvm-bugs]

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

            Bug ID: 43764
           Summary: Unqualified name use causes ambiguity through ADL
                    (forward_as_tuple)
           Product: libc++
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: All Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: marcin.zalewski at gmail.com
                CC: llvm-bugs at lists.llvm.org, mclow.lists at gmail.com

I have a library that redefines forward_as_tuple in its namespace, along with
some concrete types. This causes the problem with the following code:

https://github.com/llvm/llvm-project/blob/master/libcxx/include/tuple#L1352
https://github.com/llvm/llvm-project/blob/master/libcxx/include/tuple#L1367

Here, forward_as_tuple is being called unqualified, and ADL kicks in. ADL finds
the definition of forward_as_tuple in the library that I am using, and I get
ambiguity.

-- 
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/20191023/356ad1f3/attachment.html>