I've spotted a couple of places where we don't properly short-circuit when an error occurs, and instead we attempt to go on as if everything went right. For example, here.
To avoid littering the code with Go-style if (err) return;, maybe we can use a macro to act as "monadic do". It's probably not worth it, though.
The example is helpful, but this sounds like we need to do an audit of key methods where anything approaching that pattern is in use. Reclassifying as a bug.
I've spotted a couple of places where we don't properly short-circuit when an error occurs, and instead we attempt to go on as if everything went right. For example, here.
To avoid littering the code with Go-style
if (err) return;
, maybe we can use a macro to act as "monadic do". It's probably not worth it, though.┆Issue is synchronized with this Jira Bug by Unito