Error Message Details - Githubissues

Mercerenies commented 3 years ago

Right now, our error messages leave a lot to be desired. They tell you, in most cases, what is wrong but not where.

When we parse the source, we have information about where in the file we are. We need to transmit this information onto ir, then onto gdscript. This is going to necessitate a significant refactoring of the core data structures in both of those modules. Errors should then be able to tap into the file position information stored in those structures.

Mercerenies commented 3 years ago

See branch error-pos for progress on this issue.

Mercerenies commented 3 years ago

Steps:

[X] A type representing position in the source code (bb3d99a)
[X] AST should keep track of source position (27f378d)
[X] IR types should keep track of source position (753f057 and 500a47c)
[X] GDScript types should keep track of source position (0b09e12, 698cd03, and 8edc3cf)
[X] GDError types should have a SourceOffset parameter (2a0f94b)
[X] PError should be able to retrieve SourceOffset from its inner error (1e9df63)
[X] Wrapper around error types which converts SourceOffset to SourcePos (8572ae7)
[X] Pretty-printing the error with the SourcePos (496fb3c)

Mercerenies commented 3 years ago

496fb3c closes this issue.

Mercerenies / gdlisp

Error Message Details #45