JetBrains plans to drop some scripting-related applied sciences from the Kotlin language, together with REPL performance, an out of date API for Java scripting, the KotlinScriptMojo Maven plugin, and the kotlin-scripting-ide-services library for implementing code completion performance.
In a November 19 weblog put up, JetBrains stated it could drop these scripting applied sciences from Kotlin as a result of its analysis confirmed that person wants have been coated by different applied sciences already being supported. The scripting-related parts and libraries to be faraway from the Kotlin compiler and IntelliJ IDEA IDE embrace:
- Default REPL implementations within the Kotlin compiler and IntelliJ IDEA plugin can be sunsetted. The performance is proscribed and bettering it has not been a precedence, JetBrains stated. The corporate will proceed to advertise the Kotlin Pocket book plugin and IDE Scratch information as options for interactive Kotlin improvement. Plans name for protecting some REPL-related performance within the compiler and the Customized Scripting API. However with a last swap to the K2 compiler, a good portion of this performance can be dropped or modified.
- Java Specification Request 223, providing scripting for the Java platform. With the unique specification having been withdrawn, JetBrains doesn’t consider supporting a de facto out of date API is smart. The prevailing implementation will proceed to perform till the discharge of Kotlin 2.3 within the language model 1.9 compatibility mode.
- KotlinScriptMojo, a Maven plugin that helps script execution throughout a Maven construct. JetBrains didn’t discover proof of sufficient utilization to proceed sustaining it, so plans name for dropping it in upcoming Kotlin releases.
- kotlin-scripting-ide-services, a library for implementing code completion performance, primarily for REPL implementations. It’s at present utilized in initiatives like Kotlin Interactive. As a result of it’s closely based mostly on the infrastructure of the pre-K2 compiler it can’t simply be ported to the K2 model. Subsequently, it should almost definitely cease working across the launch of Kotlin 2.3 and can be faraway from the code base. JetBrains might think about reimplementing comparable performance on high of K2 sooner or later.
Kotlin scripting stays a necessary a part of the Kotlin infrastructure, JetBrains stated. The corporate will proceed to help it in an experimental state.
