[Bug-kawa] [bug #39947] Bad resolution of java.util.HashSet.addAll()

[Per Bothner]

Update of bug #39947 (project kawa):

                  Status:                    None => Fixed                  
             Assigned to:                    None => bothner                
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #1:

There are actually 3 methods - which a newer version of Kawa shows:
/home/bothner/Kawa/work1/testsuite/sva39947.scm:2:3: warning - more than one
definitely applicable method `addAll' in java.util.HashSet
  candidate: boolean
java.util.AbstractCollection.addAll(java.util.Collection)
  candidate: boolean java.util.Collection.addAll(java.util.Collection)
  candidate: boolean java.util.Set.addAll(java.util.Collection)

The Java Languages Specification v 3 section 15.12.2.5 "Choosing the Most
Specific Method" has special rules (near the end) for disambiguating this
situation, when all except possibly one of the methods are abstract.  I
implemented (an approximation) of these rules.  I checked that in, along with
the test-case, which now works. Thanks!


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?39947>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/