Named companion objects let you give a special name to the companion object inside a class. This helps you organize code and call its members clearly.
Named companion objects in Kotlin
class ClassName { companion object Name { // members here } }
The keyword companion object creates a singleton object inside the class.
Giving it a name is optional but useful for clarity.
MyClass.greet().class MyClass { companion object { fun greet() = "Hello" } }
Factory. You call members as MyClass.Factory.create().class MyClass { companion object Factory { fun create() = MyClass() } }
This program defines a class Car with a named companion object Builder. The build function creates a new Car. In main, we call Car.Builder.build() to create a car and print it.
class Car { companion object Builder { fun build() = Car() } } fun main() { val myCar = Car.Builder.build() println("Car created: $myCar") }
The printed Car@<hashcode> is the default string representation of the object.
You can omit the name if you don't need to distinguish the companion object.
Named companion objects help clarify code and indicate the purpose of the companion object.
Named companion objects give a clear name to the singleton object inside a class.
They help organize and call companion members clearly.
Use them to improve code readability and avoid confusion.
Practice
Solution
Step 1: Understand companion objects
Companion objects are singletons inside a class used to hold members related to the class itself.Step 2: Purpose of naming companion objects
Giving a name to a companion object helps to clearly identify and access its members, improving code readability.Final Answer:
To give a clear and specific name to the singleton object inside a class -> Option AQuick Check:
Named companion object = clear singleton name [OK]
- Thinking companion objects create multiple instances
- Confusing naming with inheritance
- Assuming naming restricts access
Solution
Step 1: Recall correct companion object syntax
The correct syntax is 'companion object Name { ... }' inside the class.Step 2: Check each option
class MyClass { companion object Named { fun greet() = "Hi" } } matches the correct syntax exactly. Others have misplaced keywords or wrong order.Final Answer:
class MyClass { companion object Named { fun greet() = "Hi" } } -> Option CQuick Check:
companion object Name { } syntax [OK]
- Swapping 'object' and 'companion' keywords
- Writing 'companionobject' as one word
- Placing the name before 'companion'
class Box {
companion object Factory {
fun create() = "Box created"
}
}
fun main() {
println(Box.Factory.create())
}Solution
Step 1: Understand named companion object usage
The companion object named 'Factory' holds the function 'create' which returns "Box created".Step 2: Analyze the main function call
Calling 'Box.Factory.create()' accesses the named companion object and calls 'create', printing "Box created".Final Answer:
Box created -> Option BQuick Check:
Box.Factory.create() prints "Box created" [OK]
- Trying to call create() without Factory prefix
- Expecting 'Factory created' output
- Confusing syntax causing compile errors
class Sample {
companion object Companion {
fun info() = "Info"
}
}
fun main() {
println(Sample.companion.info())
}Solution
Step 1: Check companion object name and usage
The companion object is named 'Companion' with uppercase C.Step 2: Analyze the call in main()
The code calls 'Sample.companion.info()' with lowercase 'companion', which does not match the name and causes a compile error.Final Answer:
Incorrect companion object name usage; should be 'Companion' not 'companion' -> Option AQuick Check:
Use exact companion object name when calling [OK]
- Using lowercase 'companion' instead of named object
- Forgetting 'object' keyword
- Assuming companion functions must be static
Logger with a named companion object Factory that provides a method create() returning a new Logger instance. Which code correctly implements this?Solution
Step 1: Recall correct syntax for named companion object
The correct syntax is 'companion object Factory { ... }' inside the class.Step 2: Check method implementation
The method 'create()' returns a new instance of Logger using 'Logger()'. class Logger { companion object Factory { fun create() = Logger() } } matches both syntax and logic.Final Answer:
class Logger { companion object Factory { fun create() = Logger() } } -> Option DQuick Check:
Named companion object with factory method = class Logger { companion object Factory { fun create() = Logger() } } [OK]
- Swapping 'object' and 'companion' keywords
- Omitting the companion object name
- Incorrect order of keywords
Ready to prove it?
Pass the test and this pattern moves unknown
