Bad scope resolution in the type-checking

[GoogleCodeExporter]

Currently, the type-checking tries to work his way up the interface's 
inheritance tree to resolve the scope of an item.

It then selects the first one to match, instead of going on to check whether it 
could be an ambiguous declaration.

Since we chose to be strict on these aspects, we should not resolve but output 
an error telling it's ambiguous, with the prospects for the resolution, to help 
fix the issue.

Original issue reported on code.google.com by dav.pineau@gmail.com on 3 Mar 2012 at 12:56

• Merged into: #36

[GoogleCodeExporter]

Original comment by dav.pineau@gmail.com on 13 Apr 2012 at 11:32

• Changed state: Accepted
• Added labels: Component-Compiler, Milestone-Release1.0, Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

This was fixed while adding tests for the issue #36

Original comment by dav.pineau@gmail.com on 7 Jul 2012 at 6:58

• Changed state: Duplicate