why if I use an unamed context parameter this isn'...

# getting-started

[elect]

why if I use an unamed context parameter this isn't available for resolution?

import org.gradle.api.Project
import java.io.ByteArrayOutputStream

context(_: Project)
operator fun String.invoke(vararg args: String): String {
    val output = ByteArrayOutputStream()
    providers.exec { // error, `providers` unresolved
        commandLine("arduino-cli", "version")
        standardOutput = output
    }
    return output.toString()
}

[elect]

if I use the named one, then it's fine

import org.gradle.api.Project
import java.io.ByteArrayOutputStream

context(project: Project)
operator fun String.invoke(vararg args: String): String {
    val output = ByteArrayOutputStream()
    project.providers.exec {
        commandLine("arduino-cli", "version")
        standardOutput = output
    }
    return output.toString()
}

[Youssef Shoaib [MOD]]

Simple: make a bridge function/property:

context(p: Project) val providers get() = p.providers

[elect]

but why?
Shouldnt this work out of the box?

public interface Project { 

    ProviderFactory getProviders();

[Youssef Shoaib [MOD]]

It's an intentional change. It's to prevent scope pollution by context parameters. You have to explicitly make these bridge methods if you deem them fit.
Btw, you can also do: contextOf<Project>().providers.exec instead of making a bridge method

[elect]

but the docs say so:

You can use _ as a context parameter name. In this case, the parameter's value is available for resolution but is not accessible by name inside the block:

[elect]

or am I getting it wrong?

[Youssef Shoaib [MOD]]

It's available for resolution as a context parameter, not as a receiver. This was the biggest change between context receivers and context parameters