Why do we use "companion object" as a kind of replacement for Java static fields in Kotlin?

Very important

To access the important data of the forums, you must be active in each forum and especially in the leaks and database leaks section, send data and after sending the data and activity, data and important content will be opened and visible for you.
You will only see chat messages from people who are at or below your level.
More than 500,000 database leaks and millions of account leaks are waiting for you, so access and view with more activity.
Many important data are inactive and inaccessible for you, so open them with activity. (This will be done automatically)

Thread Rating:

293 Vote(s) - 3.49 Average
1
2
3
4
5

Options

Why do we use "companion object" as a kind of replacement for Java static fields in Kotlin?

abriannaujggusmwwb

Valued member

Posts: 0
Threads: 0
Joined: Aug 2022
Reputation: 0

Level: inf [ Level

]
Total Points: inf
Rank nan / 1
100% to upload Level

Activity inf / 1
99% to upload your Rank

Experience nan
100% to upload Experience

Points: 50

07-20-2023, 09:03 AM

What is the intended meaning of "companion object"? So far I have been using it just to replace Java's `static` when I need it.

I am confused with:

- Why is it called "companion"?
- Does it mean that to create multiple _static_ properties, I have to group it together inside `companion object` block?
- To instantly create a singleton instance that is scoped to a class, I often write

:

companion object {
val singleton by lazy { ... }
}

which seems like an unidiomatic way of doing it. What's the better way?

« Next Oldest

Next Newest »

Forum Jump:

Users browsing this thread:

1 Guest(s)