- 
                Notifications
    
You must be signed in to change notification settings  - Fork 15.1k
 
Closed as not planned
Labels
bugzillaIssues migrated from bugzillaIssues migrated from bugzillac++14clang:frontendLanguage frontend issues, e.g. anything involving "Sema"Language frontend issues, e.g. anything involving "Sema"duplicateResolved as duplicateResolved as duplicate
Description
| Bugzilla Link | 26850 | 
| Version | unspecified | 
| OS | Windows NT | 
| Reporter | LLVM Bugzilla Contributor | 
| CC | @riccibruno | 
Extended Description
Consider the following reduced code example from a StackOverflow question:
struct X{};
struct Y{};
struct B
{
    void operator[](X){}
};
struct C
{
    void operator[](Y){}
};
struct D : B, C {};
int main()
{
    D d;
    d[Y()];
}
The call to D::operator[] should be ambiguous due to the two different base class overloads. A call to d.operator[](Y()) would correctly fail to compile.
Metadata
Metadata
Assignees
Labels
bugzillaIssues migrated from bugzillaIssues migrated from bugzillac++14clang:frontendLanguage frontend issues, e.g. anything involving "Sema"Language frontend issues, e.g. anything involving "Sema"duplicateResolved as duplicateResolved as duplicate