You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
funmain() {
val x = {} // lambda$0val y = {} // lambda$1val z = {} // lambda$2
}
funmain() {
val x = { // lambda$2val a = {} // lambda$2$lambda$0 val b = {} // lambda$2$lambda$1
}
val y = {} // lambda$3val 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
funmain() {
val x = { // lambda$0val a = {} // lambda$0$0 val b = {} // lambda$0$1
}
val y = {} // lambda$1val z = {} // lambda$2
}
The text was updated successfully, but these errors were encountered:
Given the following example:
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
The text was updated successfully, but these errors were encountered: