Hullaballoonatic
07/10/2019, 3:16 AMinterface Foo {
var recentBar: Int
protected val onBar: (Int) -> Int
fun bar(x: Int): Int {
recentBar = onBar(x)
return recentBar
}
}
I don't intend this as a suggestion, per say, hence why posting here. I assume there's an important (paradigmatic?) reason I'm missing for why such a suggestion is a terrible idea.Dariusz Kuc
07/10/2019, 3:22 AMAll abstract, default, and static methods in an interface are implicitly public, so you can omit the public modifier.
All constant values defined in an interface are implicitly public, static, and final
Hullaballoonatic
07/10/2019, 3:24 AMDariusz Kuc
07/10/2019, 3:24 AMHullaballoonatic
07/10/2019, 3:25 AMDariusz Kuc
07/10/2019, 3:25 AMjw
07/10/2019, 3:25 AMepabst
07/10/2019, 4:57 AMPaulius Ruminas
07/10/2019, 5:43 AMAl Warren
07/10/2019, 2:08 PMHullaballoonatic
07/10/2019, 2:55 PMPaulius Ruminas
07/10/2019, 4:49 PMI was under the impression interfaces were designed to prevent multiple inheritance and the diamond of death.True but do interfaces really solve those problems? 🙂
Hullaballoonatic
07/10/2019, 4:52 PMAl Warren
07/10/2019, 5:04 PMHullaballoonatic
07/10/2019, 5:06 PM