JetBrains plans to take away some scripting-related applied sciences from the kotlin languagetogether with REPL performance, a deprecated API for Java scripting, the KotlinScriptMojo Maven plugin, and the kotlin-scripting-ide-services library to implement code completion performance.
in a Weblog put up from November 19JetBrains mentioned it will take away these scripting applied sciences from Kotlin as a result of its analysis confirmed that consumer wants had been coated by different applied sciences that had been already supported. Scripting-related parts and libraries that will likely be faraway from the Kotlin compiler and the IntelliJ IDEA IDE embody:
- The default REPL implementations within the Kotlin compiler and IntelliJ IDEA plugin will likely be gone. The performance is restricted and bettering it has not been a precedence, JetBrains mentioned. The corporate will proceed to advertise the Kotlin Pocket book plugin and Scratch IDE information as options for interactive Kotlin improvement. Plans name for sustaining some REPL-related options within the compiler and customized scripting API. However with a remaining change to the k2 compilerA good portion of this performance will likely be eliminated or modified.
- Java Specification Request 223which supplies scripting for the Java platform. With the unique specification being retired, JetBrains doesn’t consider it is smart to help a de facto out of date API. The present implementation will proceed to work till the discharge of Kotlin 2.3 in language model 1.9 compatibility mode.
- KotlinScriptMojo, a Maven plugin that helps operating scripts throughout a Maven construct. JetBrains didn’t discover sufficient proof of use to proceed sustaining it, so plans name for eradicating it in future variations of Kotlin.
- kotlin-scripting-ide-services, a library for implementing code completion performance, primarily for REPL implementations. It’s presently utilized in tasks comparable to Kotlin Interactive. As a result of it depends closely on pre-K2 compiler infrastructure, it can’t be simply ported to the K2 model. Subsequently, it should probably cease working with the discharge of Kotlin 2.3 and will likely be faraway from the codebase. JetBrains might think about re-implementing related performance on high of K2 sooner or later.
Kotlin scripts stay an important a part of the Kotlin infrastructure, JetBrains mentioned. The corporate will proceed to help it in an experimental state.
