You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently in edge cases when there's an ambiguous match e.g.
java.io.File.new('.').listFiles { ... } (2 method exists that accept a single function-interface argument)
no matter the passed Proc's arity the FileFilter#accept(File) seems to be used (with a warning being printed) while with { |arg1, arg2| } we can assume that FilenameFilter#accept(File, String) is more desired than the FileFilter#accept(File)
UPDATE: which method will be used will currently depend on env (returned method order)!
The text was updated successfully, but these errors were encountered:
... of the block (see jruby#3136) when there are 2 method with different
interface type signature we can improve current (unpredictable) logic
state prior to this commit is printing a ambiguous warning, the picked
method depends on returned getMethods order
kares
added a commit
to kares/jruby
that referenced
this issue
Jul 16, 2015
so that we cache correctly cases with proc-to-iface dispatch
(per Proc's arity)
as a side effect redundant null checks were removed
and the calculation should now compute the same when using args[]
or the overloaded version (with args splatted)
(closing jruby#3136)
... of the block (see #3136) when there are 2 method with different
interface type signature we can improve current (unpredictable) logic
state prior to this commit is printing a ambiguous warning, the picked
method depends on returned getMethods order
so that we cache correctly cases with proc-to-iface dispatch
(per Proc's arity)
as a side effect redundant null checks were removed
and the calculation should now compute the same when using args[]
or the overloaded version (with args splatted)
(closing #3136)
currently in edge cases when there's an ambiguous match e.g.
java.io.File.new('.').listFiles { ... }
(2 method exists that accept a single function-interface argument)no matter the passed Proc's arity the
FileFilter#accept(File)
seems to be used (with a warning being printed) while with{ |arg1, arg2| }
we can assume thatFilenameFilter#accept(File, String)
is more desired than theFileFilter#accept(File)
UPDATE: which method will be used will currently depend on env (returned method order)!
The text was updated successfully, but these errors were encountered: