From c0d39cdde9df7866cd727b0b79c27c6f9b5021a8 Mon Sep 17 00:00:00 2001 From: Evgenii Akentev Date: Sun, 31 Jan 2021 22:56:49 +0300 Subject: [PATCH] fix link --- content/posts/implementations-of-the-handle-pattern.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/posts/implementations-of-the-handle-pattern.md b/content/posts/implementations-of-the-handle-pattern.md index 88657ab..0f5b724 100644 --- a/content/posts/implementations-of-the-handle-pattern.md +++ b/content/posts/implementations-of-the-handle-pattern.md @@ -655,4 +655,4 @@ No surprises here. Backpack works as expected specifying things at compile time. The Handle allows us to hide dependencies and to create interfaces, allowing us to easily replace the implementation without changes on the client-side — statically using Backpack for better performance or dynamically using records or alternatives in runtime (in first-class modules manner). Backpack might be too tedious for Handles that depend on each other but in simple cases, it introduces not much additional cost compared to records. And it's possible to mix them. -This post inspired me to write a follow-up post on [Backpack, modules, and records](/thoughts-on-backpack-modules-and-records). +This post inspired me to write a follow-up post on [Backpack, modules, and records](/posts/thoughts-on-backpack-modules-and-records). -- 2.50.1