fun <R> f(property: KProperty0<R>): MetaFeature<R> (source)
Creates a MetaFeature for the given property => use p in case of ambiguity issues.
Notice for assertion function writers: you should use ExpectImpl.feature and pass a
class reference instead of using this convenience function (e.g. ExpectImpl.feature(List<Int>::size)).
This way we are always able to report the property, even if the subject is not defined which occurs if a
previous transformation of the subject could not be carried out.
fun <R> f(f: KFunction0<R>): MetaFeature<R> (source)
Creates a MetaFeature for the given function f without arguments => use f0 in case of ambiguity issues.
Notice for assertion function writers: you should use ExpectImpl.feature and pass a
class reference instead of using this convenience function (e.g. ExpectImpl.feature(MyClass::fun)).
This way we are always able to report the function name, even if the subject is not defined which occurs if a
previous transformation of the subject could not be carried out.
fun <A1, R> f(f: KFunction1<A1, R>, a1: A1): MetaFeature<R> (source)
Creates a MetaFeature for the given function f which expects 1 argument => use f1 in case of ambiguity issues.
Notice for assertion function writers: you should use ExpectImpl.feature and pass a
class reference instead of using this convenience function (e.g. ExpectImpl.feature(MyClass::fun, ...)).
This way we are always able to report the function name, even if the subject is not defined which occurs if a
previous transformation of the subject could not be carried out.
fun <A1, A2, R> f(f: KFunction2<A1, A2, R>, a1: A1, a2: A2): MetaFeature<R> (source)
Creates a MetaFeature for the given function f which expects 2 arguments => use f2 in case of ambiguity issues.
Notice for assertion function writers: you should use ExpectImpl.feature and pass a
class reference instead of using this convenience function (e.g. ExpectImpl.feature(MyClass::fun, ...)).
This way we are always able to report the function name, even if the subject is not defined which occurs if a
previous transformation of the subject could not be carried out.
fun <A1, A2, A3, R> f(f: KFunction3<A1, A2, A3, R>, a1: A1, a2: A2, a3: A3): MetaFeature<R> (source)
Creates a MetaFeature for the given function f which expects 3 arguments => use f3 in case of ambiguity issues.
Notice for assertion function writers: you should use ExpectImpl.feature and pass a
class reference instead of using this convenience function (e.g. ExpectImpl.feature(MyClass::fun, ...)).
This way we are always able to report the function name, even if the subject is not defined which occurs if a
previous transformation of the subject could not be carried out.
fun <A1, A2, A3, A4, R> f(f: KFunction4<A1, A2, A3, A4, R>, a1: A1, a2: A2, a3: A3, a4: A4): MetaFeature<R> (source)
Creates a MetaFeature for the given function f which expects 4 arguments => use f4 in case of ambiguity issues.
Notice for assertion function writers: you should use ExpectImpl.feature and pass a
class reference instead of using this convenience function (e.g. ExpectImpl.feature(MyClass::fun, ...)).
This way we are always able to report the function name, even if the subject is not defined which occurs if a
previous transformation of the subject could not be carried out.
fun <A1, A2, A3, A4, A5, R> f(f: KFunction5<A1, A2, A3, A4, A5, R>, a1: A1, a2: A2, a3: A3, a4: A4, a5: A5): MetaFeature<R> (source)
Creates a MetaFeature for the given function f which expects 5 arguments => use f5 in case of ambiguity issues.
Notice for assertion function writers: you should use ExpectImpl.feature and pass a
class reference instead of using this convenience function (e.g. ExpectImpl.feature(MyClass::fun, ...)).
This way we are always able to report the function name, even if the subject is not defined which occurs if a
previous transformation of the subject could not be carried out.