`deriving Repr` no longer required for structures?

Please quote the text that is incorrect:

https://lean-lang.org/functional_programming_in_lean/getting-to-know/structures.html

If the deriving Repr line in Point's definition were omitted, then attempting #eval origin would yield an error similar to that which occurs when omitting a function's argument:

expression
origin
has type
Point
but instance
Lean.MetaEval Point
failed to be synthesized, this instance instructs Lean on how to display the resulting value, recall that any type implementing the Repr class also implements the Lean.MetaEval class

That message is saying that the evaluation machinery doesn't know how to communicate the result of evaluation back to the user.

In what way is this incorrect?

This appears to be outdated / no longer true for the current version of Lean - Even when the deriving Repr line is omitted, it's able to read and print the { ... } syntax without issues.

https://live.lean-lang.org/#codez=M4FwTgrgxiFgpgAgAoHsCWA7EiDuALeBAKEUQA9EAuRAMQBtUBDEUxAT2rsZeLYBN4AM0Sow6AOZYuaLDioBeRAG9yixAAYANB3UaAvmwDE8AG5N6o8VMxA

I suppose it's good practice to include the declaration anyway, but this had me confused me for a while, thinking I had misunderstood some part of the syntax.

Start with the quoted passage in the structures chapter at the linked Functional Programming in Lean page, then reproduce the example in the linked Lean playground with and without deriving Repr. Confirm the behavior for the current Lean version and update the explanation so it matches the result while preserving any guidance about when declaring Repr is useful.