darkmoon_uk
07/15/2023, 2:07 AMexpect
/ actual
wizard creates actuals with the convention <name>.<platform>.kt
. I'm familiar with the need to disambiguate the file's JVM name at times; is this naming convention a clear resolution on that problem? Is it documented anywhere? Thanks.agrosner
07/15/2023, 2:10 AMdarkmoon_uk
07/15/2023, 2:13 AMmbonnin
07/15/2023, 2:10 PMURL.desktop.kt
creates a desktop.kt
file in the URL
package 😒darkmoon_uk
07/15/2023, 2:44 PMdarkmoon_uk
07/15/2023, 2:45 PMUrl
this was just a contrived example)mbonnin
07/15/2023, 2:46 PMmbonnin
07/15/2023, 2:46 PMJeff Lockhart
07/15/2023, 2:51 PM-
? I've seen different conventions in many libraries.
I've also noticed kotlinx libraries often don't use the standard source set file structure, opting for module/common/src
and module/jvm/test
, for example. Maybe that's just legacy, but it's actually nice having main and test source sets grouped together.
I've just been coming up with my own file naming without putting much thought into a good standard for my own libraries. It'd make sense to standardize on something more widely accepted. I've definitely run into the JVM filename collision error often myself, so I may adopt this name.platform.kt
pattern.mbonnin
07/15/2023, 2:53 PMwhen might you prefix a file withThat's when you want to hide your API from Java. This makes sure the?-
-FooKt
file can't be called from JavaJeff Lockhart
07/15/2023, 4:27 PMmbonnin
07/15/2023, 4:29 PM