Menu
As properties' getter or setter don't usually have function as argument nor reified type, what would be the benefits / use case of using inline properties?
If the benefits would be to reduce cost related to method call, why not make all properties getter/setter inline by default?
Kotlin Inline Properties
Eg.
val foo: Foo
inline get() = Foo()
var bar: Bar
get() = ...
inline set(v) { ... }
340
Inline functions are useful when a function accepts another function or lambda as a parameter. You can use an inline function when you need to prevent "object creation" and have better control flow.
An inline class is a special type of class defined in Kotlin that only has one property. At runtime, the compiler will “inline” the property where it was used. This is similar to inline functions, where the compiler inserts the contents of the function into where it was called.
The first argument is the target object, the second argument is the actual argument passed to the function. Creating the infix function is just like creating the inline function. The only difference in syntax is that we use the infix keyword instead of inline .
Kotlin will generate a backing field for a property if we use at least one default accessor or we reference the field identifier inside a custom accessor. Default accessors are those that are generated with val or var keywords.
Here is inline properties discussion:
Example of reified type parameter:
inline val <reified T : PsiElement> T.nextSiblingOfSameType: T? get() = PsiTreeUtil.getNextSiblingOfType(this, T::class.java)Another use case is to hide some properties from the binary interface of a library. In Kotlin standard library, together with the
@InlineOnlyannotation this might make it possible in the future to exclude declarations of such properties from class files, reducing method count, this will mostly benefit Android with it's 64K method limit.
183
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
