== Why is this an issue?

Passing a collection as an argument to the collection's own method is either an error - some other argument was intended - or simply nonsensical code. 

Further, because some methods require that the argument remain unmodified during the execution, passing a collection to itself can result in undefined behavior. 

== How to fix it

=== Code examples

==== Noncompliant code example

[source,kotlin,diff-id=1,diff-type=noncompliant]
----
val objs = mutableListOf<Any>()
objs.add("Hello")

objs.add(objs) // Noncompliant; StackOverflowException if objs.hashCode() called
objs.addAll(objs) // Noncompliant; behavior undefined
objs.containsAll(objs) // Noncompliant; always true
objs.removeAll(objs) // Noncompliant; confusing. Use clear() instead
objs.retainAll(objs) // Noncompliant; NOOP
----

==== Compliant solution

[source,kotlin,diff-id=1,diff-type=compliant]
----
val newList = mutableListOf<Any>()
val objs = mutableListOf<Any>()
objs.add("Hello")

objs.containsAll(newList) // Compliant
objs.addAll(newList) // Compliant
objs.removeAll(newList) // Compliant
objs.retainAll(newList) // Compliant
----

