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

[K2] Fix functional type and improve logging for unresolved link #3157

Merged

Conversation

vmishenev
Copy link
Contributor

For example
typealias CompletionHandler = (cause: Throwable?) -> Unit has a functional type with no type arguments in K2. In K1 we have a usual generic type

For example
`typealias CompletionHandler = (cause: Throwable?) -> Unit`
has functional type with no type arguments in K2. In K1 we have a usual generic type
@@ -111,7 +111,10 @@ internal class AnnotationTranslator {
DRI(packageName = "", classNames = ERROR_CLASS_NAME)
)

KtUnsupportedAnnotationValue -> TODO()
KtUnsupportedAnnotationValue -> ClassValue(
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Incorrect input source code should not lead to an exception.

@vmishenev vmishenev marked this pull request as ready for review September 1, 2023 23:19
@vmishenev vmishenev merged commit e9e8fbf into master Sep 4, 2023
9 checks passed
@vmishenev vmishenev deleted the Fix-functional-type-and-improve-logging-for-unresolved-link branch September 4, 2023 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants