A modern programming language that makes developers happier.

kotlinlang

Hey composers, is `onActive` and `onCommit` etc still considered effects? Just the documentation for `onActive` starts with "
```An effect used to observe the lifecycle of the composition. ```
So just wondering so I know what I am talking about when discussing this :laughing:

It's on our list of terms to revisit for sure. Those two in particular probably have more claim to the name, "effect" than anything else so far as they're things that will happen if and when a composition lands. As we start playing more with multithreading composition this will get more important

I almost want to reserve `effect {}` as the name for a variant of the same idea that accepts a `suspend` lambda and will cancel the associated coroutine on disposal; it makes for a really slick API for some things