Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kotlin DSL accessors generation could recover generics form type erasure in some cases #10766

Closed
eskatos opened this issue Sep 18, 2019 · 2 comments
Labels

Comments

@eskatos
Copy link
Member

eskatos commented Sep 18, 2019

The Kotlin DSL project schema accessibility provider maps any type with generics to Any because of type erasure. However it should be possible to recover the generic type information in some cases like for SAM of lambda classes.

Expected Behavior

// in `some` plugin
project.extensions.add("some", { name: String -> name.capitalize() })
// build.gradle.kts
plugins { `some` }
require(some("foo") == "Foo")

Current Behavior

// in `some` plugin
project.extensions.add("some", { name: String -> name.capitalize() })
// build.gradle.kts
plugins { `some` }
// casting is required because `some` is typed `Any` because of type erasure
val casted = some as (String) -> String
require(casted("foo") == "Foo")

Context

#10729

@stale
Copy link

stale bot commented Oct 22, 2020

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

@stale stale bot added the stale label Oct 22, 2020
@stale
Copy link

stale bot commented Nov 12, 2020

This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request.

@stale stale bot closed this as completed Nov 12, 2020
@wolfs wolfs closed this as not planned Won't fix, can't repro, duplicate, stale Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants