From 8530359ce440f21fdb705b2dbe3506d37db3e458 Mon Sep 17 00:00:00 2001 From: Lasse Martin Jakobsen Date: Thu, 11 Jul 2019 13:20:14 +0200 Subject: [PATCH] Update README.md Co-Authored-By: Aleksandr H --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d2d6314..b16c8a0 100644 --- a/README.md +++ b/README.md @@ -1087,7 +1087,7 @@ var _ io.Writer = &NullWriter{} var _ io.Reader = &NullWriter{} ``` -From the above code, it's very easy to understand which interfaces must be fulfilled and will ensure that the compiler is helping us out on compile time. Therefore, this is generally the preferred solution for checking interface contract fulfillment. +From the above code, it's very easy to understand which interfaces must be fulfilled; this ensures that the compiler will help us out during compile time. Therefore, this is generally the preferred solution for checking interface contract fulfillment. There's yet another method of trying to be more explicit about which interfaces a given struct implements. However, this third method actually achieves the opposite of what we want. It involves using embedded interfaces as a struct property.