Also, for libs I see two special use-cases: For many published (e.g. open-source)

lib

projects it might be possible to build for absolutely all targets that Kotlin supports. Can’t we have an

all

platform, maybe with an

exclude

option? And similarly,

ios

and

macos

etc. platform shortcuts. Breaking changes about the meaning of those shortcuts would be expected and absolutely OK. So if

iosSimulatorArm64

gets added to

ios

later, that really is the desired behavior. I’d rather always attempt to build for the full set of platforms than forget some platform. Especially if my lib only relies on the stdlib (e.g. because it’s a Base64 implementation or a MIME types DB or an XML parser or …). Having to explicitly list all targets is bad for the open-source library ecosystem and it’s really only necessary when your lib contains platform-specific code. Such libs can still maintain an explicit list of supported platforms, but ideally exclusion-based, so when new platforms get supported the developers notice that by default without having to read the Kotlin “What’s new” section.

thanks, we are evaluating this possibility