memory-leaks

Still reachable: lots of words in many pages.
git clone https://git.kevinlegouguec.net/memory-leaks
Log | Files | Refs | README | LICENSE

commit acde1884cafdda6626171b66a4d824b498b090bd
parent 72ed1b208d4fd148ea45e56f1d2b2378790f7d7d
Author: Kévin Le Gouguec <kevin.legouguec@gmail.com>
Date:   Sun, 19 Apr 2020 17:51:30 +0200

Clarify some wording

Diffstat:
Mreviews/blog-roll.md | 10+++++-----
1 file changed, 5 insertions(+), 5 deletions(-)

diff --git 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