Thanks for reporting this.
EndOfLine is a built-in module, so the intended usage is one of its shared properties, for example:
EndOfLine.Native
EndOfLine.Windows
EndOfLine.macOS
EndOfLine.Linux
EndOfLine.Unix
Bare EndOfLine was being treated as the module/type itself, which is why it could show up as <class EndOfLine> in output. That was confusing, so I’ve fixed the compiler diagnostic generically rather than special-casing EndOfLine.
In the next release, using a bare type or module name where a runtime value is expected will produce a clearer compiler error and, where possible, suggest a shared member such as EndOfLine.Native.
I also fixed the stale TextArea docs example that showed bare EndOfLine.
https://feedback.objo.dev/bug/532