kotlin-fork

azalea/kotlin-fork

Fork 0

Commit Graph

Author	SHA1	Message	Date
Denis Zharkov	3bdfd811e8	Add some new String methods in JDK 11 to built-ins mapping blacklist These three methods are conflicting with existing extensions, thus the behavior might be changed when switching to JDK 11 Probably, it's worth revisiting our strategy here, e.g. by blacklisting all new methods in #KT-24974 Fixed	2018-08-31 10:33:09 +03:00
Denis Zharkov	e90c92f8d3	Separate additional built-in members from JDK into three groups - White list: can be used as common built-in declaration - Black list: can be used only for overrides and super-calls- - Not considered members: ones that is not in black or white list. Such members can be used in any context, but they usages marked as deprecated Third kind is needed to make possible use declarations added in future JDK versions. Deprecation is necessary because they may get into black list in next Kotlin compiler version	2016-05-16 15:38:13 +03:00

Author

SHA1

Message

Date

Denis Zharkov

3bdfd811e8

Add some new String methods in JDK 11 to built-ins mapping blacklist

These three methods are conflicting with existing extensions,
thus the behavior might be changed when switching to JDK 11

Probably, it's worth revisiting our strategy here,
e.g. by blacklisting all new methods in

 #KT-24974 Fixed

2018-08-31 10:33:09 +03:00

Denis Zharkov

e90c92f8d3

Separate additional built-in members from JDK into three groups

- White list: can be used as common built-in declaration
- Black list: can be used only for overrides and super-calls-
- Not considered members: ones that is not in black or white list.
Such members can be used in any context, but they usages marked as deprecated

Third kind is needed to make possible use declarations added in future JDK versions.
Deprecation is necessary because they may get into black list in next Kotlin compiler version

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

2 Commits