[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.

Ouvrez le tutoriel Tic-tac-toe lié à la section « Why immutability is important » et comparez-le avec l’article référencé « Updating Objects in State ». Mettez à jour le tutoriel pour expliquer qu’une mutation directe peut empêcher React de détecter de manière fiable les changements et d’effectuer un nouveau rendu, puis vérifiez que l’explication s’intègre à la discussion existante sur slice(), le time travel et les performances.