`Erasing state when props change` shouldn't be called "Anti-pattern"

If we rename mail to defaultMail in that example, I think the component's behavior makes sense. And this pattern also has no conflict with Alternative 1 and Alternative 2 both. Even it's more convenient, because we don't have to update id or key when passing a new default value.
In fact， this pattern doesn't cause any new problem.

从标题为 "Erasing state when props change" 的文档示例开始，并将其措辞与 Alternative 1 和 Alternative 2 进行比较。检查该示例是否应使用 defaultMail，以及将此模式称为反模式是否准确；当示例和指导反映出已达成一致的术语时，即视为完成。