as it may have no primary constructor (only actual class has it).
Refactor & rename Fir2IrGeneratorUtils.kt as having 'Fir' in stacktrace
when actual K2 compiler is not used is very confusing.
Fixes https://github.com/Kotlin/kotlinx.serialization/issues/2134
#KT-55683 Fixed
as consuming coroutines 1.4.3-native-mt is no longer compatible with
current KGP version. Since it transitively depends on
old atomicfu of version 0.15.1. And that atomicfu library was published
with experimental publication model by old Multiplatform Gradle Plugin
for MPP test. As they were way too old and no longer compatible with
MPP plugin because of the experimental publication model that were used
in earlier versions.
This behavior is incorrect and it is not supported by new
resolvable metadata dependencies configurations.
Because this configuration is expected to be resolved to metadata
artifacts only. And the fact that it gets resolvled to some platform
variant is not right. But is not critical as well.
The next steps is to remove metadata configurations from platform
source sets.
...dependency is in current build or not. Because for IDE import it
matters that it is a source dependency. While for CLI it is not
since included builds will produce an actual klib that will be transformed
Scoped metadata dependencies are not needed since
metadata dependencies are used only for metadata compilation. Metadata
is not consumed at runtime. Therefore, scoped metadata dependencies
are not required.
^KT-55312
Test uses light distribution and builds platform libs that
require Xcode at least 14.1.
Merge-request: KT-MR-8243
Merged-by: Pavel Punegov <Pavel.Punegov@jetbrains.com>
This commit supports `objcExportDisableSwiftMemberNameMangling=true`
binary option, which disables mangling for Swift names in generated
Objective-C headers, but keeps mangling for Objective-C names.
Enabling it might cause issues in some cases with actual clashes.
^KT-53638 Fixed
This file is generated even if there's no problems since Gradle 7.4. It now contains useful information to determine configuration inputs. Rely on the configuration cache problems option instead.
#KT-52625 In Progress
Otherwise `debug/stepping/enum.kt` starts failing as soon as we advance
default language version to 1.9, because with the introduction of enum
entries, enum's `<clinit>` now invokes LambdaMetafactory which invokes
its own bundled version of ASM located in
`jdk.internal.org.objectweb.asm`, so we end up stepping over a lot of
internal ASM code.
`jdk.internal.*` is also excluded by default in the debugger settings in
IntelliJ, so users will not observe this issue in practice.
Leonid Startsev