[Swift] Do we need the key parameter the BackStackItem?

[JustinDSN]

One question we're noticing on #workflow-ios Slack, is do we need the key parameter for the BackStackScreen.Item?

[AquaGeek]

I think we do need this (depending on where things land with KeyedScreen). There are legitimate use cases where you render multiple screens of the same type but different keys.

[rjrjr]

In Kotlin this concern is decoupled from BackStack, and is pretty fundamental. My impression is that it's a lot easier to create custom containers in Kotlin, and this is a pretty big part of the reason. See:

• https://github.com/square/workflow-kotlin/blob/main/workflow-ui/core-common/src/main/java/com/squareup/workflow1/ui/Compatible.kt
• https://github.com/square/workflow-kotlin/blob/main/workflow-ui/core-common/src/main/java/com/squareup/workflow1/ui/NamedScreen.kt
• https://github.com/square/workflow-kotlin/blob/main/workflow-ui/core-android/src/main/java/com/squareup/workflow1/ui/WorkflowViewStub.kt