Maybe already covered but would it make sense to e...
# multiplatformj
James Ward
09/21/2023, 4:34 AMMaybe already covered but would it make sense to enable running
commonTestj
jw
09/21/2023, 4:52 AMHow would they run? Common code is only considered common because it's a subset of a set of selected targets.
👍 3
👍🏻 1
👍🏾 1
j
James Ward
09/21/2023, 5:39 PMTheoretically couldn't we have a Kotlin/Common runtime that has no platform?
j
jw
09/21/2023, 5:41 PMWhat semantics would it have though? Would it be single threaded like JS and WASM or multithreaded like JVM and native? What actuals would be used for expect definitions?
jw
09/21/2023, 5:42 PMThere's no definition for common Kotlin because common actually means common-to-your-defined-targets. A project with only iOS and macOS targets can access Darwin APIs in common, for example.
jw
09/21/2023, 5:44 PMMoreover the addition of new targets can change what common means. If you only support JVM and native you can use things like runBlocking from coroutines in common. But if you add JS or WASM that now fails to compile because those targets don't support it.
j
James Ward
09/21/2023, 5:45 PMYeah, expects couldn't work, but could non-expects work? ie. could you test
1 + 1 == 2j
jw
09/21/2023, 5:48 PMI think the closest you could get is constant expressions and constant functions where the compiler defines a subset of the language that can be interpreted at compile time with platform-agnostic semantics.
https://youtrack.jetbrains.com/issue/KT-14652