From 87de5a031ede9d62336964b18f5a3f6634efb1f2 Mon Sep 17 00:00:00 2001 From: Honza Date: Sun, 1 Oct 2023 23:25:30 +0200 Subject: [PATCH] Update index.md (#722) --- .../fundamentals-v3/05-structural-vs-nominal-types/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/website/content/blog/fundamentals-v3/05-structural-vs-nominal-types/index.md b/packages/website/content/blog/fundamentals-v3/05-structural-vs-nominal-types/index.md index 2649ec7ee..e149e746c 100644 --- a/packages/website/content/blog/fundamentals-v3/05-structural-vs-nominal-types/index.md +++ b/packages/website/content/blog/fundamentals-v3/05-structural-vs-nominal-types/index.md @@ -151,7 +151,7 @@ If the argument passed to it meets these requirements, `printCar` is happy. "Duck typing" gets its name from the "duck test". -> “If it looks like a duck, swims like a duck, and quack like a duck, then it probably is a duck”. +> “If it looks like a duck, swims like a duck, and quack like a duck, then it probably is a duck.” In practice, this is very similar to structural typing, but "Duck typing" is usually used to describe dynamic type systems.