You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In many cases the exception classes do not receive an ASTNode object, therefore the error reporting can not provide a line number of the error (which is not very helpful in many cases):
ResolveVisitor caught error in null: ...
instead of
ResolveVisitor caught error in line 7, char 13: ...
The problem is that those exceptions are thrown inside the Scope class, which does not have any node objects associated, thus there is no node to pass to the exception object.
Any suggestions are appreciated.
The text was updated successfully, but these errors were encountered:
I'm not sure if I understand the discussion correctly. You suggested that "proper error messages via populated exceptions is a good reason to pass them in."
You mean passing an ASTNode to the resolve methods? How is this different from what lpradel did?
In many cases the exception classes do not receive an ASTNode object, therefore the error reporting can not provide a line number of the error (which is not very helpful in many cases):
instead of
The problem is that those exceptions are thrown inside the Scope class, which does not have any node objects associated, thus there is no node to pass to the exception object.
Any suggestions are appreciated.
The text was updated successfully, but these errors were encountered: