A modern programming language that makes developers happier.

kotlinlang

I'm not clear on whats the default policy on how to model `Nav3` navkeys - should they be `data object`s or data classes with random uuids attached to them (always)?

In official samples I see data objects, but this way there is no way to replace backstack (and the per entry states reset)

If I go from [a, b, c] to replace it with [c, d, e] and I have per entry viewmodels, `c` viewmodel will survive such change,which is not expected, atleast not by default I`d say.

And to pick and choose where to pepper the uuids doesnt scale, will lead to silent issues with deeplinks for example

So..whats the stance? Should every stateful nav entry have navkey with random uuid? And also, maybe something lighter thatn uuid generation? Auto increment ids counter will break with process restore, right?
