Can I know more about why `1.9.20` had to break its APIs by preventing methods with default paramete...

# kotlin-native

[Benoit Quenaudon]

Can I know more about why 1.9.20 had to break its APIs by preventing methods with default parameters in KMP? What were the limitations?

[kevin.cianfarini]

Can you be more specific? I use default params in common code in 1.9.21 with no issue.

[Benoit Quenaudon]

They’re not available anymore in expect/actual

[Benoit Quenaudon]

Or is it a bug?

[Benoit Quenaudon]

In any case it prevents me from typealiasing to OkHttp.Response because it has default parameters

[russhwolf]

Did that work prior to 1.9.20? I think the idea is the default param is redundant in the actual because it's present in the expect.

[Benoit Quenaudon]

It worked before, yes. Bumping Kotlin forces us to move away from the typealias

[russhwolf]

Does it do what you want if you drop the default param from the actual?

[Benoit Quenaudon]

The point is I don’t wanna have to write the actual. I was doing actual typealias GrpcResponse = okhttp3.Response before and I cannot anymore.

https://github.com/square/wire/pull/2820/files#diff-a68db64645006122528e3dc68b001ecb884f3f3a7b5ea882dbaca9941a5e4e09

[russhwolf]

I'm not clear what the typealias issue is specifically but there were some restrictions added around expect classes as part of stabilizing KMP.

[russhwolf]

You can try exploring the tickets linked here for some context
https://youtrack.jetbrains.com/issue/KT-56991/Expect-actual-stabilisation-in-the-scope-of-stable-KMP

[russhwolf]

Not sure if you'll find your specific issue or not

[Benoit Quenaudon]

Thank you