IssueTracker

Currently we use Modifier.composed in many places to 'wrap' modifiers with a new InspectorInfo, while ignoring any infos used internally in the implementation detail of the modifiers.

For example, Modifier.selectable currently looks like:

composed(
    factory = {
        Modifier.clickable(
            enabled = enabled,
            role = role,
            interactionSource = interactionSource,
            indication = indication,
            onClick = onClick
        ).semantics {
            this.selected = selected
        }
    },
    inspectorInfo = debugInspectorInfo {
        name = "selectable"
        properties["selected"] = selected
        properties["enabled"] = enabled
        properties["role"] = role
        properties["interactionSource"] = interactionSource
        properties["indication"] = indication
        properties["onClick"] = onClick
    }
)

In this case using composed is important, as we want to hide the clickable's InspectorInfo, and replace it with a more meaningful one for selectable.

However, using Modifier.composed like this when there are no Composable functions being called in the implementation is expensive - it means that the modifier can never be skipped, and this can cause performance degradation. As a result, this shouldn't be composed, and we will need a new specific API to ignore the internal info.