From 4d65cb233858a52facd10abb9fd3400994dd2ec3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Pedro=20Pi=C3=B1era=20Buend=C3=ADa?=
 <663605+pepicrft@users.noreply.github.com>
Date: Wed, 5 Jun 2024 08:56:59 +0200
Subject: [PATCH] Update 2024-06-04-why-you-need-objc.md

---
 priv/posts/2024-06-04-why-you-need-objc.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/priv/posts/2024-06-04-why-you-need-objc.md b/priv/posts/2024-06-04-why-you-need-objc.md
index 343b04e..1f02bf0 100644
--- a/priv/posts/2024-06-04-why-you-need-objc.md
+++ b/priv/posts/2024-06-04-why-you-need-objc.md
@@ -17,8 +17,7 @@ the problem is that the linker **overoptimizes the binary removing symbols that
 The linker's dead-stripping logic can't delete dynamically referenced symbols.
 And this is something that happens not only when referencing Objective-C symbols, but [Swift too](https://forums.swift.org/t/linker-flag-objc-force-loads-swift-libraries/47466/3).
 For example, when integrating Composable Architecture,
-which [uses](https://github.com/pointfreeco/swift-composable-architecture/blob/7cbde3b07f193f732e256429e1351ff53cd31641/Sources/ComposableArchitecture/UIKit/NSObject%2BObservation.swift#L172) Objective-C runtime capabilities,
-developers might need to add explicit references to those symbols or add the aforementioned flags to the build settings when using Tuist's default integration via Xcode targets.
+when integrating it with Tuist via Xcode targets, developers might need to add explicit references to those symbols or the flags above to the build settings.
 
 What's the solution? There are a few options: