What if your program could instantly keep only unique items without you lifting a finger?
Why Set creation (setOf, mutableSetOf) in Kotlin? - Purpose & Use Cases
Imagine you have a list of items and you want to keep only unique ones, like a guest list where no name should appear twice. Doing this by checking each item manually is like crossing names off a paper list one by one.
Manually checking for duplicates is slow and easy to mess up. You might forget to check some items or accidentally add duplicates, making your list messy and unreliable.
Kotlin's setOf and mutableSetOf create collections that automatically keep only unique items. This means you don't have to worry about duplicates--they are handled for you, saving time and avoiding mistakes.
val uniqueItems = mutableListOf<String>() for (item in items) { if (!uniqueItems.contains(item)) { uniqueItems.add(item) } }
val uniqueItems = setOf("apple", "banana", "apple")
You can easily manage collections of unique items without extra code, making your programs cleaner and more reliable.
When building a contact app, you want to store phone numbers without duplicates. Using setOf ensures each number is saved only once, avoiding confusion and errors.
Manual duplicate checks are slow and error-prone.
setOf and mutableSetOf handle uniqueness automatically.
This makes your code simpler and your data cleaner.
Practice
setOf(1, 2, 2, 3) return?Solution
Step 1: Understand
setOfbehaviorsetOfcreates a set that holds only unique elements, automatically removing duplicates.Step 2: Analyze the input elements
The input has elements 1, 2, 2, 3. The duplicate 2 is ignored in the set.Final Answer:
A set containing unique elements: 1, 2, 3 -> Option CQuick Check:
setOf removes duplicates = unique elements [OK]
- Thinking sets keep duplicates like lists
- Confusing setOf with listOf
- Expecting an error for duplicates
Solution
Step 1: Identify correct syntax for mutableSetOf
The correct function ismutableSetOfwith type parameter and parentheses.Step 2: Check each option
val mySet = mutableSetOf<String>("apple", "banana") usesmutableSetOf<String>("apple", "banana"), which is correct. val mySet = setOf<String>("apple", "banana") usessetOfwhich creates an immutable set. val mySet = mutableSet("apple", "banana") uses a non-existent functionmutableSet. val mySet = mutableSetOf("apple", "banana") has a syntax error with an extra quote.Final Answer:
val mySet = mutableSetOf<String>("apple", "banana") -> Option AQuick Check:
mutableSetOf syntax correct = val mySet = mutableSetOf<String>("apple", "banana") [OK]
- Using setOf instead of mutableSetOf for mutable sets
- Misspelling mutableSetOf
- Syntax errors with quotes or parentheses
val numbers = mutableSetOf(1, 2, 3) numbers.add(2) numbers.add(4) println(numbers)
Solution
Step 1: Understand mutableSetOf and add behavior
The set starts with 1, 2, 3. Adding 2 again does nothing because sets ignore duplicates. Adding 4 adds a new element.Step 2: Determine final set contents
After additions, the set contains 1, 2, 3, and 4.Final Answer:
[1, 2, 3, 4] -> Option DQuick Check:
Sets ignore duplicates, so 2 is not added twice [OK]
- Expecting duplicates to appear in output
- Confusing set print format with list
- Thinking add returns error on duplicates
val fruits = setOf("apple", "banana")
fruits.add("orange")
println(fruits)Solution
Step 1: Check mutability of setOf
setOfcreates an immutable set that cannot be changed after creation.Step 2: Analyze the add operation
Callingaddon an immutable set causes a compilation error because the set cannot be modified.Final Answer:
Cannot add elements to an immutable set -> Option BQuick Check:
setOf = immutable, add() not allowed [OK]
- Trying to modify immutable sets
- Confusing setOf with mutableSetOf
- Ignoring compiler error messages
Solution
Step 1: Understand filtering and set creation
We want a mutable set with only numbers > 5. UsingfilterTowith a mutable set collects filtered items directly into a mutable set.Step 2: Evaluate each option
val nums = mutableSetOf(1, 6, 8, 3, 7).filter { it > 5 } returns a List, not a mutable set. val nums = mutableSetOf(1, 6, 8, 3, 7).filterTo(mutableSetOf()) { it > 5 } correctly filters into a mutable set. val nums = setOf(1, 6, 8, 3, 7).filter { it > 5 }.toSet() creates an immutable set first, then filters to list and toSet(), producing an immutable set, not mutable. val nums = mutableSetOf(1, 6, 8, 3, 7).filter { it > 5 }.toSet() filters to a list then toSet(), producing an immutable set, not mutable.Final Answer:
val nums = mutableSetOf(1, 6, 8, 3, 7).filterTo(mutableSetOf()) { it > 5 } -> Option AQuick Check:
filterTo with mutableSetOf creates mutable set directly [OK]
- Using filter() returns list, not set
- Not converting to mutable set after filtering
- Confusing setOf and mutableSetOf usage
Ready to prove it?
Pass the test and this pattern moves unknown
