Is changing a `public fun` to `public inline fun` ...
# announcements
r
Is changing a
public fun
to
public inline fun
binary and source compatible?
i
Yes it should be. The inverse however (inline -> not inline) is not source compatible.
r
Thank you, that's what I thought, but wanted to confirm!
i
Note also that changing
inline
to
inline
+
reified
is not binary compatible
k
Why isn't the reverse source compatible?
r
Because an inline fun can do things a non-inline fun can't e.g. contain suspending functions if the call-site is suspending
Or non-local returns
k
Forgot about those 😏.