Is there a reason `kotlin.abiValidation` couldn't ...

# gradle

[mbonnin]

Is there a reason kotlin.abiValidation couldn't be a type safe fun abiValidation(action: Action<AbiValidationExtension>) ?
I get that working with extensions is best for top level blocks because of Groovy interop but is it also needed for nested blocks?
Reason I'm asking is it hurts discoverability when working in convention plugins where generated accessors are not always available.

[Vampire]

Probably because it is not always present.
That extension is only created if ABI validation is actually enabled (i.e. not disabled using kotlin.abi.validation.disabled)

[mbonnin]

Follow up question is why would I disable it
(there is also kotlin.abiValidation.enabled)

[mbonnin]

Might be an optimisation to simplify the Gradle model for projects where it's not enabled

[mbonnin]

But if that's the case, why not make it like

kotlin {
  jvm() // tasks are created here
}

?

[mbonnin]

Or is there some other reason?