Conversation
I think this discussion is relevant: maplibre/maplibre-java#40 (comment) It concerns overloads with default parameters, so, applies to this change. |
|
Interesting, so this means that someone calling this via Objective-C would not get the additional constructor? But any Kotlin -> Kotlin/Native code will still have it, right? The readme says "supports Kotlin Multiplatform and Java projects", so I'd consider Objective-C and Swift outside of the scope of this library. |
|
KMP has been improving Swift export lately, so I could see this improving through the compiler over time since Swift does support defaults. In the meantime, well:
Very curious about the state of existing Turf ports on Swift. Would a swift export of this library be useful to that ecosystem? |
Not sure why these were separate.
@JvmOverloadstakes care of the Java overload, and the small extra branch is cheap. Technically, altitude now gets boxed when it's passed, but thanks to arena allocators I'd be shocked if that matters in practice.