Change format + fix for --richerrors

[vzarytovskii]

For some reason, I didn't include the --richerrors flag when committing yesterday.

Also, changed format to use ASCII characters + look a bit more different, in the format:

error FSXXXX: <Error message>
  --> /path/to/file.fsx
  1 | let context = error
					^^^^^

[github-actions]

❗ Release notes required

@vzarytovskii,

Caution

No release notes found for the changed paths (see table below).

Please make sure to add an entry with an informative description of the change as well as link to this pull request, issue and language suggestion if applicable. Release notes for this repository are based on Keep A Changelog format.

The following format is recommended for this repository:

* <Informative description>. ([PR #XXXXX](https://github.com/dotnet/fsharp/pull/XXXXX))

See examples in the files, listed in the table below or in th full documentation at https://fsharp.github.io/fsharp-compiler-docs/release-notes/About.html.

If you believe that release notes are not necessary for this PR, please add NO_RELEASE_NOTES label to the pull request.

You can open this PR in browser to add release notes: open in github.dev

Change path	Release notes path	Description
src/Compiler	docs/release-notes/.FSharp.Compiler.Service/9.0.100.md	No release notes found or release notes format is not correct

[vzarytovskii]

/run fantomas

[github-actions]

Ran fantomas: https://github.com/dotnet/fsharp/actions/runs/10577802291

[psfinaki]

Bubbles are gone, I'm happy

[edgarfgp]

What are your thoughts on having something similar to Gleam compiler errors. ?

Source: https://gleam.run/news/fault-tolerant-gleam/

[vzarytovskii]

What are your thoughts on having something similar to Gleam compiler errors. ?

Source: https://gleam.run/news/fault-tolerant-gleam/

This is what we having pretty much, except simpler presentation. Can change it in further PRs. And as for messaging - we don't have that information at this point. We currently only have number, message and context.

[edgarfgp]

What are your thoughts on having something similar to Gleam compiler errors. ?

Source: https://gleam.run/news/fault-tolerant-gleam/

This is what we having pretty much, except simpler presentation. Can change it in further PRs. And as for messaging - we don't have that information at this point. We currently only have number, message and context.

@vzarytovskii
I guess we could

• Replace the absolute path with a relative path
• Replace -> | with 「 to simply this.

Regarding we don't have that information at this point

• Would ExtendedData to FSharpDiagnostic help here Add ExtendedData to FSharpDiagnostic #15840 ?

[vzarytovskii]

What are your thoughts on having something similar to Gleam compiler errors. ?

Source: https://gleam.run/news/fault-tolerant-gleam/

This is what we having pretty much, except simpler presentation. Can change it in further PRs. And as for messaging - we don't have that information at this point. We currently only have number, message and context.

@vzarytovskii

I guess we could

• Replace the absolute path with a relative path

I can do that where possible.

• Replace -> | with 「 to simply this.

I personally think that standard easily typeable symbols read better, but we can try and see how it looks.

Regarding we don't have that information at this point

• Would ExtendedData to FSharpDiagnostic help here Add ExtendedData to FSharpDiagnostic #15840 ?

I will and it won't at the same time, info from it can be used, but it needs to be plumbed there, and it'll either need to be processed case by case where to put it or provide pairs of range-message to automatically print. In other words there needs to be a new mechanism introduced which will be responsible for providing additional contextual info, which can be printed without the need to know how it's structured.

[edgarfgp]

What are your thoughts on having something similar to Gleam compiler errors. ?

Source: https://gleam.run/news/fault-tolerant-gleam/

This is what we having pretty much, except simpler presentation. Can change it in further PRs. And as for messaging - we don't have that information at this point. We currently only have number, message and context.

@vzarytovskii I guess we could

• Replace the absolute path with a relative path
• Replace -> | with 「 to simply this.

Regarding we don't have that information at this point

• Would ExtendedData to FSharpDiagnostic help here Add ExtendedData to FSharpDiagnostic #15840 ?

Sounds like we will need a plan/document to formalise this new approach, So we can incrementally improve this.