Is there any method in kotlin which replaces below two line into one. I know i can create a extension function but I'm eager to know if it already exist in kotlin. Something like listOfChecklist.clearAndAddAll()
.
listOfChecklist.clear()
listOfChecklist.addAll(newList)
This is what I'm doing now manually using an extension function. But I hope there is a better solution.
fun <E> MutableCollection<E>.clearAndAddAll(replace: MutableSet<E>) {
clear()
addAll(replace)
}
To add a single element to a list or a set, use the add() function. The specified object is appended to the end of the collection. addAll() adds every element of the argument object to a list or a set. The argument can be an Iterable , a Sequence , or an Array .
First, we create an empty ArrayList to store the strings. Next, we add a few fruits to the ArrayList object, using the add() method such as: "Apple" , "Mango" , "Grapes" , and "Orange" . Next, we call the clear() method and it removes all the elements from the Arraylist .
It's not possible to do this. An idiomatic way to solve your case would be using a scope function like with
.
val list = mutableListOf<String>()
with(list){
clear()
addAll(arrayListOf())
}
My answer will be rather philosophical, so here are my thoughts:
If you really feel the need to merge these 2 operations into one line of code, it suggests you use this very often.
If you use this design pattern very often, it seems to me that there is something quite wrong in your overall design of your application/class and here I totally agree with the "I hope there's no such method" comment by @miensol.
If you don't use it often, I think that leaving it on 2 lines of code makes it much more readable.
Clearing the "listOfChecklist" makes sense only if "newlist" gets cleared at some point too, otherwise you could just keep the reference like: "listOfChecklist = newlist" and boom! You're done ...
If you use mutable lists a lot, which are being cleared and their elements are being copied between each other, again, it seem to me as an over-use of mutable state, which makes your code difficult to reason about. I would suggest to look at some core functional programming principles which will get you rid of the clear/addAll concerns completely :-).
I am not a performance expert, but for most of the use cases I don't really see a reasonable benefit of reusing an existing list instead of just simply cloning it (if you really need to keep the elements for some reason) and speaking of performance itself, the JVM almost always does a good job anyway.
Conclusion: What I would suggest is to keep it on 2 lines if you really need it or design your code in a way so that you completely avoid the need for clear/addAll. Otherwise you can just go with your extension function or whatever makes you feel happy.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With