Property vs Field

Definitely, as the title suggests that Properties and Fields are separate things.

I would extend this with “memory backing” aspect to: “In Kotlin, field is only used when needed as a part of a property to hold property value in memory. Fields can not be declared directly.”

For the sake of smaller edits, how about this change:

In Kotlin, field is only used when needed as a part of a property to hold a property value in memory. Fields can not be declared directly.

An “a” was added before the 16th word. Single character-beat that! :rofl:

In Kotlin, a field is only used when needed as a part of a property to hold a property value in memory. Fields can not be declared directly

Technically two characters are changed since you removed the trailing punctuation :wink:

I added the punctuation back. Smallest change so far :wink:

Lol nice. Here’s one smaller. I italicized the “b” in “be declared”, no characters added/removed!

In Kotlin, a field is only used when needed as a part of a property to hold a property value in memory. Fields can not be declared directly.


Can a mod split this topic? Either at the post right after the 2 year jump or at my post from a day ago?

1 Like

I created a PR to apply the changes we discussed here:

1 Like

@yvolk since you started this discussion again I would like you to take a look at my PR and give some feedback. Do you think those changes are enough or should we add more explanation there?

Thank you @Wasabi375 I think these changes are enough to avoid noticed confusion.

@Wasabi375 After we changed the target page title in the merge request #1931, I noticed that we forgot to change titles of the links to that page.
Now I created PR for that: Fix link titles referring to the "Properties" page by yvolk · Pull Request #2012 · JetBrains/kotlin-web-site · GitHub

3 Likes