Provide proper platformSpecficContainer in CompositePlatformConfigurator
Now, call 'configureDefaultCheckers' and 'configureExtensionsAndCheckers' from all childs configurators, instead of taking just container from CommonPlatformAnalyzerServices This is needed because some IDE services tend to re-create containers (in particular, PerFileAnalysisCache and ResolveElementCache do that to re-inject new trace) and use usual injection DSL, which, in particular, takes 'platformSpecificContainer'. Returning 'common'-conatiner leads to losing all platform-specific checkers. On the other hand, calling exactly 'configureDefaultCheckers' + 'configureExtensionsAndCheckers' should be correct, because that's how single-platform 'platformSpecificContainer' is composed (see PlatformConfiguratorBase), and in 'createContainerForCompositePlatform' we don't use 'platformSpecificContainer' anyways ^KT-23305 Fixed
This commit is contained in:
@@ -0,0 +1,7 @@
|
||||
// !DIAGNOSTICS: -ABSTRACT_MEMBER_NOT_IMPLEMENTED
|
||||
|
||||
// Implementing kotlin functions isn't allowed on JS
|
||||
class <!IMPLEMENTING_FUNCTION_INTERFACE!>A<!> : (Int) -> Int
|
||||
|
||||
// Array as upper bound isn't allowed on JVM
|
||||
class B<<!UPPER_BOUND_CANNOT_BE_ARRAY!>T : Array<*><!>>
|
||||
@@ -0,0 +1 @@
|
||||
MODULE common { platform=[JS, JVM, Native] }
|
||||
Reference in New Issue
Block a user