| commit | c732b71b8b4192b605b02b7c5c3da14743a5815d | [log] [tgz] |
|---|---|---|
| author | Russ Cox <rsc@golang.org> | Thu Aug 01 17:30:13 2019 -0400 |
| committer | Russ Cox <rsc@golang.org> | Thu Aug 01 21:30:45 2019 +0000 |
| tree | 2d966f3963832707fc74869d55801f12fa38a750 | |
| parent | 33144fd1b52b7c6762251251bcbdd6b2c2e8a992 [diff] |
content/experiment: fix typo Change-Id: Ic3710a19aef5d26f28a5f873e5c6e6b57347c248 Reviewed-on: https://go-review.googlesource.com/c/blog/+/188617 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Russ Cox <rsc@golang.org>
diff --git a/content/experiment.article b/content/experiment.article index a38bee2..f25726e 100644 --- a/content/experiment.article +++ b/content/experiment.article
@@ -565,7 +565,7 @@ Whether to make it possible to unwrap an error is an API decision, the same way that whether to export a struct field is an API decision. Sometimes it is appropriate to expose that detail to calling code, -and sometimes you isn’t. +and sometimes it isn’t. When it is, implement Unwrap. When it isn’t, don’t implement Unwrap.