Skip to content

Indy Lambda function names are shuffled #220

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

Open
sellmair opened this issue Jun 12, 2025 · 0 comments
Open

Indy Lambda function names are shuffled #220

sellmair opened this issue Jun 12, 2025 · 0 comments
Assignees
Labels

Comments

@sellmair
Copy link
Member

Given the following example:

fun main() {
    val x = {} // lambda$0
    val y = {} // lambda$1
    val z = {} // lambda$2
}

fun main() {
    val x = { // lambda$2
        val a = {} // lambda$2$lambda$0 
        val b = {} // lambda$2$lambda$1
    }
    val y = {} // lambda$3
    val z = {} // lambda$4
}

It is clear that nested lambdas 'shuffle' names of functions, which will escalate dirty scope resolution (e.g., adding a new nested lambda will invalidate the entire function). This dirty scope invalidation can quickly escalate to the entry point, where reloads will either fail or get rejected (See #218 )

A desirable naming schema for the functions would be

fun main() {
    val x = { // lambda$0
        val a = {} // lambda$0$0 
        val b = {} // lambda$0$1
    }
    val y = {} // lambda$1
    val z = {} // lambda$2
}
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