[Wasm] Mark JsAllowImplementingFunctionInterface with OTHER kind
This fixes test failures when advancing bootstrap. When a language feature has UNSTABLE_FEATURE kind, enabling it causes the compiler to mark the compiled library with the pre-release flag. JsAllowImplementingFunctionInterface feature is enabled by default in Wasm backend. So effectively, all Wasm klibs are marked with the pre-release flag, including the standard library. Pre-release checks were enabled recently and cause compiler errors. To fix the problem, this commit changes the feature kind to OTHER, which doesn't enforce the pre-release flag. Merge-request: KT-MR-8582 Merged-by: Svyatoslav Kuzmich <svyatoslav.kuzmich@jetbrains.com>
This commit is contained in:
committed by
Space Team
parent
fe5a8f664a
commit
e517df1533
@@ -321,7 +321,7 @@ enum class LanguageFeature(
|
||||
ValueClasses(sinceVersion = null, kind = UNSTABLE_FEATURE),
|
||||
JavaSamConversionEqualsHashCode(sinceVersion = null, kind = UNSTABLE_FEATURE),
|
||||
UnitConversionsOnArbitraryExpressions(sinceVersion = null),
|
||||
JsAllowImplementingFunctionInterface(sinceVersion = null, kind = UNSTABLE_FEATURE),
|
||||
JsAllowImplementingFunctionInterface(sinceVersion = null, kind = OTHER),
|
||||
CustomEqualsInValueClasses(sinceVersion = null, kind = OTHER), // KT-24874
|
||||
InlineLateinit(sinceVersion = null, kind = OTHER), // KT-23814
|
||||
EnableDfaWarningsInK2(sinceVersion = null, kind = OTHER), // KT-50965
|
||||
|
||||
Reference in New Issue
Block a user