Although Kotlin doesn’t provide a built-in Swift-style solution for property changes observation, you can still do it in several ways depending on what your goal is. There is observable(…) delegate (in stdlib) that allows you to handle the property changes. Usage example: var foo: String by Delegates.observable(“bar”) { property, old, new -> println(“$property has changed … Read more
Tricky, this, as there’s no one single consistent style followed by all applications. As you say they are (broadly) synonyms. In truth it doesn’t really matter so long as your expected audience understands what you mean. The biggest difference is between Properties, which usually affect a component or object, and the others, which affect the … Read more
In general terms (and in normal English usage) the terms mean the same thing. In the specific context of HTML / Javascript the terms get confused because the HTML representation of a DOM element has attributes (that being the term used in XML for the key/value pairs contained within a tag) but when represented as … Read more
Quote from The Swift Programming Language, which answers your question: “Swift’s compiler performs four helpful safety-checks to make sure that two-phase initialization is completed without error:” Safety check 1 “A designated initializer must ensure that all of the “properties introduced by its class are initialized before it delegates up to a superclass initializer.” Excerpt From: … Read more
Here are the significant differences between lateinit var and by lazy { … } delegated property: lazy { … } delegate can only be used for val properties, whereas lateinit can only be applied to vars, because it can’t be compiled to a final field, thus no immutability can be guaranteed; lateinit var has a … Read more