Discovered what appears to be a bug with the

in

operator. Below is some sample code from a prototype which doesn't work as expected if the

dataType

argument contains one or more space characters (eg " kotlin.String "):

fun processDataType(dataType: String): String {
    val kotlinBaseTypes = setOf("<http://kotlin.Int|kotlin.Int>", "kotlin.String", "kotlin.UInt")
    return if (dataType in kotlinBaseTypes) dataType.trim().replace("kotlin.", "")
    else dataType.trim()
}

I'm wondering if the issue is limited to Kotlin Native or if it affects other Kotlin platforms. Replacing

return if (dataType in kotlinBaseTypes) dataType.trim().replace("kotlin.", "")

with

return if (dataType.trim() in kotlinBaseTypes) dataType.trim().replace("kotlin.", "")

works around the issue.

how is that a bug? containers always work that way

You seem surprised that

"kotlin.String"

and

" kotlin.String "

are not the same strings, there's no bug here

Why does the

in

operator have to match the entire String? Positional matches should be covered by the

in

operator. Provided the text being matched exists in the String, the position shouldn't matter.

x in container

is equivalent to

container.contains(x)

that always means

container.any { it == x }

not

container.any { it.contains(x) }

That explains why the

in

operator doesn't behave the same way as the

contains

function.

no, the

in

operator behaves the exact same way as the

contains

function, the order of arguments is just reversed

Is there a function in the Kotlin std lib that can do text matching, where the position in the String doesn't matter?

no