Are `noinline` and `crossinline` purely used to gu...
# getting-started
e
Are
noinline
and
crossinline
purely used to guide Kotlin compilation correctness? I mean I notice in some situations, we'll need to use -
noinline
- for a nullable lambda parameter -
crossinline
- for a lambda parameter that will be used as input as another lambda of a function within the function Both seams more like to aid compiler to avoid during the wrong compilation. I wonder if there are any developer-optimization jurisdictions needed to decide if we should use
noinline
or
crossinline
? (e.g. we use
inline
to decide if we want speed vs size of app compile).
e