avoiding namespace pollution is implicit here since

@Composable

functions can only be called from other

@Composable

functions - yes, we don't want that pollution either 🙂

I know, but

state

is not a

@Composable

function

the plan is for it to become a very related construct that plays by the same rules, part of dropping the unary + operator