thanks! Imho by wrapping them (ie `IntArray`, `Dou...
# stdlib
h
thanks! Imho by wrapping them (ie
IntArray
,
DoubleArray
, etc) behind a
kotlin.collections.Iterable
like interface, their primitive nature becomes too hidden to justify sticking to Java conventions here. However, I see the point that kotlin also wants to stay consistent with java where possible, so maybe you could add an inspection to warn
IntArray.hashCode()
(etc.) users about the danger? This should not be too hard since there's a "hashCode() called on Array" inspection already for java.
👍 5