Unnecessary `$state` in "select-bindings" tutorial for static `<select>` options?

[becknik]

Hey,
I'm currently going though the official tutorial and have noticed the following thing that won't make any sense to me:

svelte.dev/apps/svelte.dev/content/tutorial/01-svelte/06-bindings/04-select-bindings/+assets/app-a/src/lib/App.svelte

Lines 2 to 15 in d382b43

	let questions = $state([
	{
	id: 1,
	text: `Where did you go to school?`
	},
	{
	id: 2,
	text: `What is your mother's name?`
	},
	{
	id: 3,
	text: `What is another personal fact that an attacker could easily find with Google?`
	}
	]);

The array here is wrapped inside a $state rune, but since it's never adjusted I'm not completely sure why that is. Removing the rune from it just seems to work flawlessly...

svelte.dev/apps/svelte.dev/content/tutorial/01-svelte/06-bindings/04-select-bindings/+assets/app-a/src/lib/App.svelte

Lines 33 to 42 in d382b43

	<select
	value={selected}
	onchange={() => (answer = '')}
	>
	{#each questions as question}
	<option value={question}>
	{question.text}
	</option>
	{/each}
	</select>

Do I miss something important/ idiomatic in Svelte, or is this indeed a small mistake?

[eltigerchino]

You're right. There's no need for it to be wrapped in $state(). Feel free to open a PR to fix this!