Skip to content
Prev 44607 / 63421 Next
Original Raw

namespace S3 and S4 generic imports cannot both be satisfied:

John Chambers 
Yes, you are right.

Mixing S3 and S4 methods for a generic is fine, although in subtle cases 
one is safer promoting the S3 method to an S4 method, as you did in your 
example.

Usually, the default method for the S4 generic is the S3 generic.  But, 
in general, it's not possible to check algorithmically whether the S3 
methods will be dispatched.  For example, an S4 method on "vector" could 
dispatch S3 methods on subclasses "numeric", etc. (don't ask why ...), 
for a generic that had no default method.

That the trouble with this check isn't found right away is likely 
because one is typically working with a primitive where no generic 
function is created.

Should be fixed in rev. 61263.  Please check on your real example; it 
seems fine on the test you submitted.

Thanks for the catch.

John
On 12/8/12 3:05 PM, Martin Morgan wrote:

Thread (3 messages)

Martin Morgan namespace S3 and S4 generic imports cannot both be satisfied: Dec 8 John Chambers namespace S3 and S4 generic imports cannot both be satisfied: Dec 9 Martin Morgan namespace S3 and S4 generic imports cannot both be satisfied: Dec 13