Svelte 5: Add warning to compiler when using `bind:value` incorrectly about svelte HOT 2 CLOSED

It is valid to not declare the value as bindable because it's valid for the property to get out of sync with its parent. Therefore closing.

from svelte.

It is valid to not declare the value as bindable because it's valid for the property to get out of sync with its parent. Therefore closing.

@dummdidumm Can you give a use-case/example where the developer intent is to bind the value, but it is still valid to let the value get out of sync with its parent? This seems to defeat the purpose of "binding" if it's not "bound".

The second case is even more baffling. How can you reliably know the result of an update operation with two different bind directives on the same element. Isn't that a clear race-condition issue that should be avoided or warned about?

from svelte.