From 5d780f9c81c0bfb015b523441e10ccc325b16a40 Mon Sep 17 00:00:00 2001 From: Ian Lance Taylor Date: Tue, 14 Feb 2023 15:09:27 -0800 Subject: go2draft-error-handling-overview: update Microsoft blog links Change-Id: I39ff235ce4b591fa93ffec4b2154abed428990ee Reviewed-on: https://go-review.googlesource.com/c/proposal/+/468395 Reviewed-by: Ian Lance Taylor Run-TryBot: Ian Lance Taylor --- design/go2draft-error-handling-overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/design/go2draft-error-handling-overview.md b/design/go2draft-error-handling-overview.md index 3ee67fd..37cef42 100644 --- a/design/go2draft-error-handling-overview.md +++ b/design/go2draft-error-handling-overview.md @@ -42,8 +42,8 @@ including C++, C#, Java, and Python—represents implicit checking of implicit r The subtleties of implicit checking are covered well in Raymond Chen’s pair of blog posts, -"[Cleaner, more elegant, and wrong](https://blogs.msdn.microsoft.com/oldnewthing/20040422-00/?p=39683)" (2004), -and "[Cleaner, more elegant, and harder to recognize](https://blogs.msdn.microsoft.com/oldnewthing/20050114-00/?p=36693)" (2005). +"[Cleaner, more elegant, and wrong](https://devblogs.microsoft.com/oldnewthing/20040422-00/?p=39683)" (2004), +and "[Cleaner, more elegant, and harder to recognize](https://devblogs.microsoft.com/oldnewthing/20050114-00/?p=36693)" (2005). In essence, because you can’t see implicit checks at all, it is very hard to verify by inspection that the error handling code correctly recovers from the state of the program at the time the check fails. -- cgit v1.3