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
Risor's compiler produces very terse error messages, which makes finding the issue in scripts spanning multiple modules difficult.
For instance, the following is an error message from a script which imports another module that is referencing an undefined variable:
$ go run ../cmd/risor main.risor
compile error: undefined variable "jfaijfeao" (line 1)
exit status 1
The error message omits the name of the module where the error has originated. It also omits the column number. Please, compare with an error produced by the parser:
$ go run ../cmd/risor main.risor
parse error: unterminated block statement
location: line 3, column 4
for{
^
exit status 1
Again, module name is not reported, though the provided information is very detailed and helps narrow down the issue to a character.
The text was updated successfully, but these errors were encountered:
Risor's compiler produces very terse error messages, which makes finding the issue in scripts spanning multiple modules difficult.
For instance, the following is an error message from a script which imports another module that is referencing an undefined variable:
The error message omits the name of the module where the error has originated. It also omits the column number. Please, compare with an error produced by the parser:
Again, module name is not reported, though the provided information is very detailed and helps narrow down the issue to a character.
The text was updated successfully, but these errors were encountered: