summaryrefslogtreecommitdiff
path: root/reviews/blog-roll.md
diff options
context:
space:
mode:
authorKévin Le Gouguec <kevin.legouguec@gmail.com>2020-04-19 17:51:30 +0200
committerKévin Le Gouguec <kevin.legouguec@gmail.com>2020-04-19 17:51:30 +0200
commitacde1884cafdda6626171b66a4d824b498b090bd (patch)
treef01b27cab31f3ff8313672762cf1f4f01a03151b /reviews/blog-roll.md
parent72ed1b208d4fd148ea45e56f1d2b2378790f7d7d (diff)
downloadmemory-leaks-acde1884cafdda6626171b66a4d824b498b090bd.tar.xz
Clarify some wording
Diffstat (limited to 'reviews/blog-roll.md')
-rw-r--r--reviews/blog-roll.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/reviews/blog-roll.md b/reviews/blog-roll.md
index 92981c2..08ffaf9 100644
--- a/reviews/blog-roll.md
+++ b/reviews/blog-roll.md
@@ -194,11 +194,11 @@ then goes over unsatisfactory models:
- **Error codes** clutter a function's signature with an extra return
value, and the resulting branches degrade performance; they do not
- automatically interrupt execution, thus when bugs finally show up,
- it can be hard to track their origin down.
- - Though they did provide their developers with an escape hatch
- that lets them ignore return values, their `ignore` keyword is
- at least auditable.
+ interrupt execution unless checked manually, thus when bugs finally
+ show up, it can be hard to track their origin down.
+ - Though the Midori team did provide their developers with an
+ escape hatch that lets them ignore return values, their `ignore`
+ keyword is at least auditable.
- **Unchecked exceptions** make it hard to reason about a program's
flow. They persist because in the grand scheme of things, they stay