Hi. For a subtree of our class hierarchy we have interface method

apply

whose argument is a SAM from guava. Since some of us started using K we bump into the conflict with Kotlin's

apply

quite often. I'm considering the resolution options and so far found only two. Did I miss anything? 1. rename member

apply

to something like

applyFunction

(involves convincing several teamleads who do not use K ) 2. specify the receiver type (

someInstanceOfBase.apply<Base> { ... }

) (suggested by @marstran) 3. accept that this is the reality and use

also

instead of

apply

4. duplicate Kotlin's

apply

and rename that (suggested by @karelpeeters) Here's the recipe for the disaster at hand 🙂 (irrelevant parts omitted for brevity) ☕

import com.google.common.base.Function;
public abstract class Base {
	public <T, F> T apply(Function<F, T> function) {
		return function.apply((F) this);
	}
}

I’m kind of curious as to what conditions the

apply

conflict occurs - any chance we could get a code sample?

@Shawn sure, I've updated the OP.