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

Rename Extension annotation to ExtensionFunctionType

Browse Source 
The old one is kept temporarily and will be removed later
This commit is contained in:
Alexander Udalov
2015-11-25 19:29:20 +03:00
parent 6d40d94127
commit 7449ad2763
36 changed files with 80 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files
spec-docs/function-types.md
+2 -2
View File
@@ -23,7 +23,7 @@ Kotlin lambdas are translated to subclasses of this abstract class, passing the
## Extension functions
Extension function type `T.(P) -> R` is now just a shorthand for `@Extension Function2<T, P, R>`.
Extension function type `T.(P) -> R` is now just a shorthand for `@ExtensionFunctionType Function2<T, P, R>`.
`kotlin.extension` is a **type annotation** defined in built-ins.
So effectively functions and extension functions now have the same type,
which means that everything which takes a function will work with an extension function and vice versa.
@@ -40,7 +40,7 @@ or an extension function expression where a function is expected and vice versa.
If you really want to do that, change the shape, assign literal to a variable or use the `as` operator.
So basically you can now safely coerce values between function and extension function types,
but still should invoke them in the format which you specified in their type (with or without `@Extension`).
but still should invoke them in the format which you specified in their type (with or without `@ExtensionFunctionType`).
With this we'll get rid of classes `ExtensionFunction0`, `ExtensionFunction1`, ...
and the rest of this article will deal only with usual functions.