Fix infinite recursion when calling to_text on an Atom with lazy field

[Akirathan]

Fixes #7138

Pull Request Description

Invoking to_text method on an atom with a lazy field may result in an infinite recursion. This PR fixes that by recognizing a lazy field, and printing it with just ~field_name, instead of evaluating it.

Important Notes

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated, if necessary.
• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Scala,
  Java,
  TypeScript,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• Unit tests have been written where possible.
• If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
  or the Snowflake database integration, a run of the Extra Tests has been scheduled.
  • If applicable, it is suggested to paste a link to a successful run of the Extra Tests.

[JaroslavTulach]

• fixes the problem - good
• however this will prevent already computed fields to be visible
• shouldn't we differentiate between computed/not yet computed lazy field?

[Akirathan]

shouldn't we differentiate between computed/not yet computed lazy field?

Done in e6242ae by introducing a new message isFieldEvaluated on StructsLibrary.

[JaroslavTulach]

shouldn't we differentiate between computed/not yet computed lazy field?

Done in e6242ae by introducing a new message isFieldEvaluated on StructsLibrary.

That's very clever idea!

• all existing messages are untouched
• default implementation of the isFieldEvaluated guarantees compatible behavior
• only (the single) implementation of the library needs to be changed to report false

Very nice evolution approach.