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

dynamic TypeParam should be equivalent to generic param #307

Closed
Schahen opened this issue Jun 10, 2020 · 0 comments · Fixed by #369
Closed

dynamic TypeParam should be equivalent to generic param #307

Schahen opened this issue Jun 10, 2020 · 0 comments · Fixed by #369
Assignees
Labels
domain:conflicting overloads ir-target causes problems with IR compilation
Milestone

Comments

@Schahen
Copy link
Contributor

Schahen commented Jun 10, 2020

Following code:

interface A<T> { }
interface B<T> { }

interface Api {
   check<T>(values: Array<T>): T
   check<T>(values: Array<A<T> | B<T>>): T
}

Is translated to:

external interface A<T>

external interface B<T>

external interface Api {
    fun <T> check(values: Array<T>): T
    fun <T> check(values: Array<dynamic /* A<T> | B<T> */>): T
}

Which won't compile without "CONFLICTING_OVERLOADS" suppression

@Schahen Schahen added the ir-target causes problems with IR compilation label Jun 10, 2020
@Schahen Schahen modified the milestones: 0.5.2, 0.5.3 Jun 10, 2020
@Schahen Schahen changed the title dynamic TypeParam should override generic param dynamic TypeParam should be equivalent to generic param Jun 16, 2020
@Schahen Schahen modified the milestones: 0.5.3, 0.5.8 Jul 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain:conflicting overloads ir-target causes problems with IR compilation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants