azalea/kotlin-fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Minor spelling changes

Browse Source
This commit is contained in:
Ilmir Usmanov
2020-09-23 14:56:28 +02:00
committed by Ilmir Usmanov
parent de3ffc4a89
commit 6a150fffe6
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
compiler/backend/src/org/jetbrains/kotlin/codegen/coroutines/coroutines-codegen.md
+4 -4
View File
@@ -1018,7 +1018,7 @@ fun main() {
the generated `create` will look like the generated `create` will look like
```kotlin ```kotlin
public fun create(value: Any?, completion: Continuation): Continuation { public fun create(value: Any?, completion: Continuation): Continuation {
val resutl = main$lambda$1(this.$i, completion) val result = main$lambda$1(this.$i, completion)
result.I$0 = value as Int result.I$0 = value as Int
} }
``` ```
@@ -1027,13 +1027,13 @@ note that the constructor, in addition to captured parameters, accepts a complet
In Old JVM BE, `create` is generated for every suspend lambda even when we do not need it. I.e., even for suspending lambdas with In Old JVM BE, `create` is generated for every suspend lambda even when we do not need it. I.e., even for suspending lambdas with
more than one parameter. There are only two versions of `createCoroutineUnintercepted`, and there are no other places where we call more than one parameter. There are only two versions of `createCoroutineUnintercepted`, and there are no other places where we call
`create` (apart from compiler-generated `invoke`s). Thus, in JVM_IR BE, we fixed the slip-up, and it generates the `create` function only `create` (apart from compiler-generated `invoke`s). Thus, in JVM_IR BE, we fixed the slip-up, and it generates the `create` function only
for functions with zero on one parameter. for functions with zero or one parameter.
##### Lambda Parameters ##### Lambda Parameters
We need to put the suspend lambda arguments into fields since there can be only one argument of `invokeSuspend` - `$result`. The compiler We need to put the suspend lambda arguments into fields since there can be only one argument of `invokeSuspend` - `$result`. The compiler
moves the lambda body into `invokeSuspend`. Thus, `invokeSuspend` does all the computation. We reuse fields for spilled variables for moves the lambda body into `invokeSuspend`. Thus, `invokeSuspend` does all the computation. We reuse fields for spilled variables for
parameters as well. For example, if we have a lambda with type `suspend Int.(Long, Any) -> Unit`, then `I$0` hold value of extension parameters as well. For example, if we have a lambda with type `suspend Int.(Long, Any) -> Unit`, then `I$0` holds value of extension
receiver,' `J$0` - the first argument, `L$1` - the second one. receiver, `J$0` - the first argument, `L$1` - the second one.
This way, we can reuse spilled variables cleanup logic for parameters. If we used separate fields for parameters, we would need to manually This way, we can reuse spilled variables cleanup logic for parameters. If we used separate fields for parameters, we would need to manually
push `null` to them as we do for spilled variable fields if we do not need them anymore. push `null` to them as we do for spilled variable fields if we do not need them anymore.