Unactionable state_referenced_locally warning when $state(prop)

[gyzerok]

Describe the bug

I think there is at least one case where having this warning now is actually weird. When you initialize state with something from props I'd argue it is expected by the definition of how both $state rune and JS works, that your value will get out of sync with that prop. So in practice there is no way out of this warning except writing ignore comments above each of such lines. Would it make sense to suppress this case?

Reproduction

REPL

Logs

System Info

irrelevant

Severity

annoyance

[gyzerok]

I think there should also be handled $state.raw rune and cases like this:

const { value } = $props()

let example = $state({ foo: value })

[gyzerok]

Another case I've found in our code is:

const { value, another = 2 * value } = $props()

Adding $derived here won't work. Should this case be managed automatically by the compiler or maybe there should be a workaround suggested in the warning?

[sillvva]

The last one is a bug according to Rich. The others are expected.

#16343 (comment)

[gyzerok]

Closed to move discussion to another issue