Hello! Is there any specific reason for absence dependency builder functions `kotlinx` to add depend...

# gradle

[Iaroslav Postovalov]

Hello! Is there any specific reason for absence dependency builder functions kotlinx to add dependencies in group org.jetbrains.kotlinx?
Possible use cases:
1. Adding dependencies by github.com/Kotlin

dependencies {
  implementation(kotlinx("coroutines-core", "1.5.1"))
}

2. Adding plugins by github.com/Kotlin

plugins {
  kotlinx("benchmark") version "0.3.1"
}

[tapchicoma]

kotlin(..) shortcut comes from Gradle kotlin-dsl , so, please, open a new Gradle issue regarding adding new shortcut

[Iaroslav Postovalov]

I just wanted to check if there is a simple reason. I'll add an issue, of course

[Iaroslav Postovalov]

https://github.com/gradle/gradle/issues/17956

[gildor]

I found that I don’t like those shortcuts, they look inconsistent with other dependency declarations, make it harder to search by dependency name and what is even worse, it adds own version if you omit version (and it will be Gradle Kotlin version, not Kotlin Plugin version), so as result you cannot explicitly omit it if you use BOM for example (I prefer fail if BOM is not applied instead of getting unexpected version of dependency in classpath)
I also think that kotlinx would be even more strange, because kotlin-dsl has nothing to do with kotlinx

In general I think that it was a mistake to add it, it’s an overuse of DSL

And all of those shortcuts become completely redundant when you use versions catalog

[Vampire]

Then open a counter-FR to remove that one 😄