Closed jcharum closed 4 years ago
Otherwise, you get a very confusing error message like:
inv1_const_map_scan@2:1 error: %!v(PANIC=Error method: runtime error: invalid memory address or nil pointer dereference)
This is because we construct a (non-nil) maybeTaskFatalErr error that holds a nil error. The error gets swallowed by reviseSeverity, so this shouldn't change computation behavior, but we've already printed the confusing error by then.
nil
maybeTaskFatalErr
reviseSeverity
Otherwise, you get a very confusing error message like:
This is because we construct a (non-
nil)maybeTaskFatalErrerror that holds anilerror. The error gets swallowed byreviseSeverity, so this shouldn't change computation behavior, but we've already printed the confusing error by then.