are top-level variables outside of a class referre...
# getting-startedf
Florian
10/04/2019, 8:25 AMare top-level variables outside of a class referred to as "properties"?
m
Matteo Mirk
10/04/2019, 8:29 AMI don’t think so, since properties are related to a class: they presume implicit accessors, which don’t exist for top level declarations. They’re just variables or constants, global or not depending on their visibility
f
Florian
10/04/2019, 8:30 AMbut they have a generated getter/setter
m
Marko Mitic
10/04/2019, 8:32 AMI assumed so
Marko Mitic
10/04/2019, 8:32 AMMarko Mitic
10/04/2019, 8:33 AMKotlin has had top-level functions and properties from day one.
m
Matteo Mirk
10/04/2019, 8:34 AMOh wow… didn’t know that, thanks!
m
Marko Mitic
10/04/2019, 8:36 AMI did test whether top-level properties were allowed last week while preparing presentation, I was interested whether one can expect/actual properties (spoiler, you can)
f
Florian
10/04/2019, 10:04 AMthank you very much
m
Mike
10/04/2019, 11:54 AM@Matteo Mirk They end up being class properties in the bytecode because there's no choice, and as per above, they add getter/setter for convenient/idiomatic access in Java.
f
Florian
10/04/2019, 1:16 PMYou can also override get/set like for class properties. Is that something that is used in real code?
m
Matteo Mirk
10/04/2019, 1:54 PMYeah, now that Marko pointed it out I know. Makes sense: translating to Java you have no other choice other than making those static members of a top-level class. Thanks for the clarification.
f
Florian
10/05/2019, 4:09 PMtop-level properties can never be declared without initialization, unless they're nullable or use lateinit/lazy, right?