[Suggestion]: Tic-tac-toe tutorial should explicitly explain that mutation causes unreliable re-rendering

Summary

The tutorial's Why immutability is important section doesn't clearly state that mutating state causes unreliable re-rendering behavior.

Page

https://react.dev/learn/tutorial-tic-tac-toe#why-immutability-is-important

Details

While following the tic-tac-toe tutorial, I was confused about why .slice() is necessary. The "Why immutability is important" section talks about time travel features and performance optimizations, but it never explains that mutating the array directly will cause React to not reliably detect the change, meaning the component may not re-render.

It seems as though that is the primary reason the tutorial uses .slice(), but it's not mentioned. I only found this explanation later in the "Updating Objects in State" article. It would be helpful to include this explanation in the tutorial where beginners first encounter the pattern.

Öffne das verlinkte Tic-tac-toe-Tutorial im Abschnitt „Why immutability is important“ und vergleiche es mit dem referenzierten Artikel „Updating Objects in State“. Aktualisiere das Tutorial, um zu erklären, dass direkte Mutation React daran hindern kann, Änderungen zuverlässig zu erkennen und erneut zu rendern, und überprüfe anschließend, dass die Erklärung zur bestehenden Diskussion über slice(), Time Travel und Performance passt.