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
fa39151 refactor: Remove unused error() (MarcoFalke)
fad0335 scripted-diff: Replace error() with LogError() (MarcoFalke)
fa808fb refactor: Make error() return type void (MarcoFalke)
fa1d624 scripted-diff: return error(...); ==> error(...); return false; (MarcoFalke)
fa9a5e8 refactor: Add missing {} around error() calls (MarcoFalke)
Pull request description:
`error(...)` has many issues:
* It is often used in the context of `return error(...)`, implying that it has a "fancy" type, creating confusion with `util::Result/Error`
* `-logsourcelocations` does not work with it, because it will pretend the error happened inside of `logging.h`
* The log line contains `ERROR: `, as opposed to `[error]`, like for other errors logged with `LogError`.
Fix all issues by removing it.
ACKs for top commit:
fjahr:
re-utACK fa39151
stickies-v:
re-ACK fa39151, no changes since 4a90374
ryanofsky:
Code review ACK fa39151. Just rebase since last review
Tree-SHA512: ec5bb502ab0d3733fdb14a8a00762638fce0417afd8dd6294ae0d485ce2b7ca5b1efeb50fc2cd7467f6c652e4ed3e99b0f283b08aeca04bbfb7ea4f2c95d283a
0 commit comments