Skip to content

Conversation

vmishenev
Copy link
Contributor

No description provided.

Copy link
Member

@IgnatBeresnev IgnatBeresnev left a comment

Choose a reason for hiding this comment

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

Could you please also do something with the unsafe list index access in KotlinSignatureProvider#486? It's from the exception in the reported issue. I don't think it should fail the build even if something wasn't resolved properly by analysis.

It could generate nothing inside parentheses and emit a warning, it could write Error class in its place (if it should've been resolved, but there's nothing there), or maybe you'll come up with some other solution

@vmishenev
Copy link
Contributor Author

Could you please also do something with the unsafe list index access in KotlinSignatureProvider#486? I

I have added a simple check on it since we have no constraints on a number of arguments in a functional type.

@vmishenev vmishenev merged commit 3d8be6c into master Dec 6, 2023
@vmishenev vmishenev deleted the vmishenev/3392-k2-fix-typealised-type branch December 6, 2023 20:48
vmishenev added a commit that referenced this pull request Mar 20, 2024
* [K2] Fix typealiased type to function

* Add check on emptiness
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.

[K2] Typealias to functional type with reciever leads to IndexOutOfBoundsException
3 participants