Is there an easier way to conditionalize Kotlin co...

# multiplatform

[Conrad Kramer]

Is there an easier way to conditionalize Kotlin code on iOS simulator versus device other than different source sets?

[Paul Woitaschek]

You can work with expect / actual

[Paul Woitaschek]

If you want to stay in commonMain land you could write an expect val isSimulator and handle the various code paths there

[Paul Woitaschek]

Or you directly have expect actual functions that no-op in different source sets

[Conrad Kramer]

Yeah, that is what I ended up doing (expect / actual with different source sets), it’s just annoying to have to split it up among several different files

[Paul Woitaschek]

So my suggestion fixes that?

[Casey Brooks]

The alternative would be something like a precompiler, which makes code difficult to read and test, which is why Kotlin doesn’t use a one.

For simple variables, something like this might help bridge the gap, though I’m not how to use to it for different values per KMPP sourceset https://github.com/gmazzo/gradle-buildconfig-plugin

[Paul Woitaschek]

I wonder what these specifics are. We have approx 40k loc multiplatform and only a handful of expect actual stuff

[Conrad Kramer]

I was about to say that BuildConfig like system would achieve what I want (runtime branching against a compile time constant)

my branching is not between one branch that compiles and one that does not at the moment, it just changing some logic

[Conrad Kramer]

I could imagine annotations built with KSP to exclude classes from a build or branch at compile time based on certain options

[Paul Woitaschek]

But why not a simple expect val isSimulator

[Paul Woitaschek]

The you can just do a if(isSimulator) doStuff else doOtherStuff