Update 'Error Handling'
parent
fb12dc478e
commit
91f5029b54
@ -2,4 +2,4 @@ There are two types of errors in the ARF compiler: errors, and warnings, both of
|
||||
|
||||
When an error bubbles up to the actual program that is driving the compilation code, it should simply print the error by passing it to a `fmt` print function, or by calling its `Error()` method. It should not attempt to cast the error to an `infoerr.Error` struct, because there is a chance it might not be.
|
||||
|
||||
When writing error messages, present the user with something very plain. Do not overload the message with technichal information. Describe what the problem is, and why it was reported.
|
||||
When writing error messages, present the user with something very plain. Do not overload the message with technichal information. Describe what the problem is, and why it was reported. In terms of descriptiveness, be the opposite of the Go compiler. In terms of clarity, be the opposite of g++.
|
Reference in New Issue
Block a user