How to contribute descriptive error messages?

[panasenco]

Let's say I get educated in what an error message really means and I want to contribute a more descriptive error message to the codebase to help future coders running into the same problem. Where would I begin?

Also, it would be amazing (but probably very difficult?) to implement error messages like Rust does.

[mthom]

incomplete_reduction often refers to a conflict between two or three operators with irreconcilable precedence/associativity. That might be a good place to start. I'm not sure what else to suggest.. I'll give it some more thought.

I wonder if the Rust team have packaged those routines out into a library we could use.

[malbarbo]

There some crates that provide diagnostic reporting like in rustc. A good start is https://github.com/brendanzab/codespan.

[UWN]

(I only found this just now)

For errors that are also exceptions please refer to this classification. The major difference is that in ISO Prolog errors state what is expected first, and not what is found.

[panasenco]

(I only found this just now)

For errors that are also exceptions please refer to this classification. The major difference is that in ISO Prolog errors state what is expected first, and not what is found.

This is an awesome reference @UWN, thank you!!