I would expect those kind of issues to be caught a...
# multiplatform
n
I would expect those kind of issues to be caught at compile time.
r
I think you'll catch it at compile-time if you build JS
k
Kind of surprised it compiled. Certainly would expect Intellij to complain
r
The IDE redlines it but gradle will let it through. I don’t really know what’s happening under the hood but the sense I get based on how it behaves is that when combining sources, the build process just cares about matching `expect`/`actual` and doesn’t pay attention to where dependencies come from. Then by the time it’s actually compiling, it has a target platform and no longer cares that the JVM dependency it’s pulling in was written into a common source file.
Letting this kind of thing through is also what lets you do things like shared native sourcesets.
e
I like this behavior.