Fix double 'the the' in various places

Author: amartini51

docs/Generics/chapters/conformance-paths.tex

@@ -1168,7 +1168,7 @@ \section{The Halting Problem}\label{tag systems}
 \end{listing}
 
 \begin{definition}
-We encode strings over the the alphabet $\{a,b,c\}$ as compositions of the below substitution maps:
+We encode strings over the alphabet $\{a,b,c\}$ as compositions of the below substitution maps:
 \begin{gather*}
 \SigmaAA := \SubstMapC{\SubstType{$\uptau$}{AA<$\uptau$>}}{\SubstConf{$\uptau$}{AA<$\uptau$>}{Tag}}\\
 \SigmaBB := \SubstMapC{\SubstType{$\uptau$}{BB<$\uptau$>}}{\SubstConf{$\uptau$}{BB<$\uptau$>}{Tag}}\\

docs/SIL/SIL.md

@@ -300,7 +300,7 @@ There are three kind of arguments:
 ```
 
 - Phi arguments: If a block has multiple predecessor blocks, the terminators of
-  the predecessor blocks must be `br` or `cond_br` instructions and the the
+  the predecessor blocks must be `br` or `cond_br` instructions and the
   operand values of those branch instructions are passed to the block's
   arguments. This corresponds to LLVM's phi nodes. Basic block arguments are
   bound by the branch from the predecessor block:

lib/Frontend/CompilerInvocation.cpp

@@ -793,7 +793,7 @@ static bool ParseEnabledFeatureArgs(LangOptions &Opts, ArgList &Args,
     if (!seenFeatures.insert(*feature).second)
       continue;
 
-    // If the the current language mode enables the feature by default then
+    // If the current language mode enables the feature by default then
     // diagnose and skip it.
     if (auto firstVersion = getFeatureLanguageVersion(*feature)) {
       if (Opts.isSwiftVersionAtLeast(*firstVersion)) {

lib/SILGen/SILGenDecl.cpp

@@ -1761,7 +1761,7 @@ SILValue SILGenFunction::emitZipperedOSVersionRangeCheck(
   VersionRange VariantOSVersion = variantRange;
 
   // We're building zippered, so we need to pass both macOS and iOS
-  // versions to the the runtime version range check. At run time
+  // versions to the runtime version range check. At run time
   // that check will determine what kind of process this code is loaded
   // into. In a macOS process it will use the macOS version; in an
   // macCatalyst process it will use the iOS version.

lib/SILGen/SILGenThunk.cpp

@@ -541,7 +541,7 @@ SILFunction *SILGenModule::getOrCreateForeignAsyncCompletionHandlerImplFunction(
         }
         auto blockParamIndex = [paramIndices](unsigned long i) {
           // The non-error, non-flag block parameter (formal types of the
-          // completion handler's arguments) indices are the same as the the
+          // completion handler's arguments) indices are the same as the
           // parameter (lowered types of the completion handler's arguments)
           // indices but shifted by 1 corresponding to the fact that the lowered
           // completion handler has a block_storage argument but the formal type

lib/SILOptimizer/Mandatory/MoveOnlyObjectCheckerUtils.cpp

@@ -414,7 +414,7 @@ void MoveOnlyObjectCheckerPImpl::check(
     }
 
     // NOTE: In the following we only rewrite lifetimes once we have emitted
-    // diagnostics. This ensures that we can emit diagnostics using the the
+    // diagnostics. This ensures that we can emit diagnostics using the
     // liveness information before rewrite lifetimes has enriched the liveness
     // info with maximized liveness information.
 

lib/Sema/TypeCheckMacros.cpp

@@ -200,7 +200,7 @@ MacroDefinition MacroDefinitionRequest::evaluate(
   if (!typeCheckedType)
     return MacroDefinition::forInvalid();
 
-  // If the expanded macro was one of the the magic literal expressions
+  // If the expanded macro was one of the magic literal expressions
   // (like #file), there's nothing to expand.
   if (isa<MagicIdentifierLiteralExpr>(definition)) {
     StringRef expansionText = externalMacroName.unbridged();

test/IRGen/reflection_metadata_isolated_any.swift

@@ -10,7 +10,7 @@
 // is fine.  Since this is for reflective metadata, we could go a step
 // further if we decide we really only care about layout equivalence for
 // these; if so, we could just suppress the @isolated(any) part of the
-// type completely, since it has the the same external layout as an
+// type completely, since it has the same external layout as an
 // ordinary function type.
 // rdar://129861211
 

unittests/AST/AvailabilityContextTests.cpp

@@ -59,7 +59,7 @@ TEST_F(AvailabilityContextTest, PlatformIntroduction) {
   stillMacOS10_9.constrainWithPlatformRange(getAvailabilityRange(10, 9), ctx);
   EXPECT_EQ(stillMacOS10_9, macOS10_9);
 
-  // Constrain the the macOS version to >= 10.10 instead. The resulting context
+  // Constrain the macOS version to >= 10.10 instead. The resulting context
   // should be a new context that is less available than the deployment target
   // context (a.k.a. "contained by").
   auto macOS10_10 = macOS10_9;

utils/swift-xcodegen/README.md

@@ -75,7 +75,7 @@ PROJECT CONFIGURATION:
                           disabled by default.
 
                           A development snapshot is necessary to avoid spurious build/live issues
-                          due to the fact that the the stdlib is built using the just-built Swift
+                          due to the fact that the stdlib is built using the just-built Swift
                           compiler, which may support features not yet supported by the Swift
                           compiler in Xcode's toolchain. (default: --no-stdlib-swift)
   --test-folders/--no-test-folders

utils/swift-xcodegen/Sources/swift-xcodegen/Options.swift

@@ -168,7 +168,7 @@ struct ProjectOptions: ParsableArguments {
       disabled by default. 
       
       A development snapshot is necessary to avoid spurious build/live issues
-      due to the fact that the the stdlib is built using the just-built Swift
+      due to the fact that the stdlib is built using the just-built Swift
       compiler, which may support features not yet supported by the Swift
       compiler in Xcode's toolchain.
       """