Which is better a `val` with a backing property or a public kotlinlang #announcements

Channels

kotlin-foundation

compose-android

ohio-kotlin-users

kotlin-by-example

sofl-user-group

kotlin-multiplatform-contest

tricity-kotlin-user-group

kotlin-in-action

android-databinding

cincinnati-user-group

fluid-libraries

codemash-precompiler

kotlingforbeginners

jhipster-kotlin

prozis-android-backup

realworldkotlin

graviton-browser

spring-security

domain-driven-design

connect-audit-events

swiss-user-group

effectivekotlin

refactoring-to-kotlin

russian-kotlinasfirst

androidgithubprojects

introduce-yourself

pocketgitclient

effective-kotlin

algolialibraries

lambdaworld_cadiz

intellij-tricks

kotlin-pakistan

navigation-architecture-component

strife-discord-lib

machinelearningbawas

leedskotlinusergroup

stayhungrystayfoolish

kotest-contributors

practical-functional-programming

swagger-gradle-codegen

100daysofkotlin

kotlinultimatechallenge

pattern-matching

kotlinforbeginners

competitive-programming

compose-ui-showcase

competitivecoding

kotlin-data-storage

skia-wasm-interop-temp

java-to-kotlin-refactoring

event21-community-content

androidx-xprocessing

embedded-kotlin

fb-internal-demo

image-processing

myndocs-oauth2-server

kotlintest-devs

beepiz-libraries

kotlinprogrammers

cscenter-course-2016

k2-early-adopters

intellij-plugins

language-proposals

library-development

refreshversions

language-evolution

kotlinx-datetime

framework-elide

compose-desktop

jvm-ir-backend-feedback

android-architecture

100daysofkotlin-2021

github-workflows-kt

python-contributors

squarelibraries

arrow-contributors

codingconventions

getting-started

Title

v

Vishnu Haridas

11/04/2019, 10:05 AM

Which is better, a

val

with a backing property, or a public property with a private setter? Is there any difference? For example,

class Foo {

    // (1) - public property with a private setter
    var isSyncing = false
        private set
    
    // (2) - val with a backing property
    private var isSyncing_ = false
    val isSyncing get() = isSyncing_
}

➕ 1

h

hallvard

11/04/2019, 10:11 AM

Did you check with javap?

✔️ 1

v

Vishnu Haridas

11/04/2019, 10:19 AM

I did a decompile from Kotlin Bytecode to Java in Android Studio. Both (1) and (2) are same.

h

hallvard

11/04/2019, 10:21 AM

🙂

v

Vishnu Haridas

11/04/2019, 10:23 AM

Just checking if there is any preference for one style over the other? 🤔

s

Stephan Schroeder

11/04/2019, 10:28 AM

hmm, i always did (2) but (1) is probabaly nicer in that it communicates that the value you get isn’t immutable.

(2) is more efficient though, because a private property is actually converted to a Java field. So it can be accessed from within the class without going through getters and setters.

b

Burkhard

11/04/2019, 10:32 AM

That is only really true for android without any of the optimizations of the jvm. final getters within the same class should just be optimized to a field access.

I personally prefer (1). It is less work to write and it shows a clearer intend. The advantage of (2) is that the backing field can have a different type eg. public get

List

and private

MutableList

👍 6

✔️ 2

8 Views

#announcements Join Slack