Denis Zharkov 5381c06936 Improve 1.0-compatibility mode for JDK dependent members ...

Just reporting error by call checker may be too restrictive
in case there are some extensions that can be used successfully

Solution is to annotate additional members with
@Deprecated(level=Error) + @kotlin.internal.LowPriorityInOverloadResolution

2016-09-22 15:40:37 +03:00

..

blackListed.kt

Separate additional built-in members from JDK into three groups

2016-05-16 15:38:13 +03:00

blackListed.txt

Separate additional built-in members from JDK into three groups

2016-05-16 15:38:13 +03:00

concurrentMapRemove.kt

Add MutableMap.remove(K, V) as built-in declaration

2016-04-29 15:08:54 +03:00

concurrentMapRemove.txt

Use signatures instead of fq-names in special built-ins

2016-04-29 15:08:54 +03:00

forEachRemainingNullability.kt

Introduce predefined enhancement info

2016-04-25 17:41:08 +03:00

forEachRemainingNullability.txt

Introduce predefined enhancement info

2016-04-25 17:41:08 +03:00

getOrDefault.kt

Add Map.getOrDefault method as PlatformDependent declaration with refined signature

2016-07-27 18:46:13 +03:00

getOrDefault.txt

Add Map.getOrDefault method as PlatformDependent declaration with refined signature

2016-07-27 18:46:13 +03:00

mutableMapRemove.kt

Add MutableMap.remove(K, V) as built-in declaration

2016-04-29 15:08:54 +03:00

mutableMapRemove.txt

Add Map.getOrDefault method as PlatformDependent declaration with refined signature

2016-07-27 18:46:13 +03:00

removeIf.kt

…

removeIf.txt

…

stream.kt

…

stream.txt

…

unsupportedFeature.kt

Improve 1.0-compatibility mode for JDK dependent members

2016-09-22 15:40:37 +03:00