This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28583 - Inherited method name conflicts with consequential maplike/setlike interfaces should fail
Summary: Inherited method name conflicts with consequential maplike/setlike interfaces...
Status: NEW
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-29 18:06 UTC by Kyle Machulis
Modified: 2015-04-29 18:06 UTC (History)
2 users (show)

See Also:

Attachments

Description Kyle Machulis 2015-04-29 18:06:46 UTC 
Consider the following interface:

interface Foo1 {
  maplike<long, long>;
};
interface Foo2 {
  void entries();
};
interface Foo3 : Foo2 {
};
Foo3 implements Foo1;

Currently, this interface passes. However, if the maplike were directly on Foo3, it would fail. The spec should probably make sure this fails, too.