Merge pull request #1087 from practicalswift/double-spaces

[gardening] Fix typos: "word[space][space]word" (two spaces) → "word[space]word" (one space)

Author: gribozavr

docs/CMakeLists.txt

@@ -82,7 +82,7 @@ if(LITRE_EXECUTABLE)
     VERBATIM
     )
 
-  # Only update the real top-level CMakeLists.txt if something  changed
+  # Only update the real top-level CMakeLists.txt if something changed
   add_custom_command(
     OUTPUT
       "litre-tests/CMakeLists.txt"

docs/ErrorHandling.rst

@@ -578,7 +578,7 @@ of failability.
 
 One limitation of this approach is that we need to be able to reconstruct
 the selector to use when an overload of a method is introduced.  For this
-reason, the import is likely to be limited to methods where  the error
+reason, the import is likely to be limited to methods where the error
 parameter is the last one and the corresponding selector
 chunk is either ``error:`` or the first chunk (see below).  Empirically,
 this seems to do the right thing for all but two sets of APIs in the

docs/TypeChecker.rst

@@ -106,7 +106,7 @@ the Swift type system:
   flavors of equality constraints: 
 
     - Exact equality constraints, or  "binding", written ``T0 := X``
-      for some type variable ``T0`` and  type ``X``, which requires
+      for some type variable ``T0`` and type ``X``, which requires
       that ``T0`` be exactly identical to ``X``;
     - Equality constraints, written ``X == Y`` for types ``X`` and
       ``Y``, which require ``X`` and ``Y`` to have the same type,

docs/archive/LangRef.html

@@ -1093,7 +1093,7 @@ <h3 id="type-function">Function Types</h3>
 
   <p>The result type of a function type must
      be <a href="#materializable">materializable</a>.  The argument type of a
-     function is always required to be parenthesized (a tuple).  The  behavior
+     function is always required to be parenthesized (a tuple).  The behavior
      of function types may be modified with the <a 
       href="#attribute-autoclosure"><tt>autoclosure</tt> attribute</a>.</p>
 

docs/doxygen.intro

@@ -4,7 +4,7 @@
 /// Welcome to Swift.
 ///
 /// This documentation describes the @b internal software that makes 
-/// up Swift, not the @b external use of  Swift. There are no instructions
+/// up Swift, not the @b external use of Swift. There are no instructions
 /// here on how to use Swift, only the APIs that make up the software. For usage 
 /// instructions, please see the programmer's guide or reference manual.
 ///

docs/proposals/OptimizerEffects.rst

@@ -482,7 +482,7 @@ destructor can have arbitrary side-effects. Therefore, it is not valid to hoist
 the makeUnique in the code without proving that 'T's destructor cannot change
 the uniqueness state. This is trivial for trivial types but requires a more
 sophisticated analysis for class types (and in general cannot be disproved). In
-following example we can only hoist makeUnique if we can prove that  elt's, and
+following example we can only hoist makeUnique if we can prove that elt's, and
 elt2's destructor can't change the uniqueness state of the arrays.::
 
  for i in 0 ..< min(a.size, b.size) {

include/swift/AST/SILOptions.h

@@ -51,7 +51,7 @@ class SILOptions {
     OptimizeUnchecked
   };
 
-  /// Controls how  perform SIL linking.
+  /// Controls how to perform SIL linking.
   LinkingMode LinkMode = LinkNormal;
 
   /// Remove all runtime assertions during optimizations.

include/swift/AST/Types.h

@@ -1924,7 +1924,7 @@ class ModuleType : public TypeBase {
 
   // Implement isa/cast/dyncast/etc.
   static bool classof(const TypeBase *T) {
-    return  T->getKind() == TypeKind::Module;
+    return T->getKind() == TypeKind::Module;
   }
 
 private:

include/swift/LLVMPasses/PassesFwd.h

@@ -1,4 +1,4 @@
-//===--- PassesFwd.h - Creation functions for LLVM  passes ------*- C++ -*-===//
+//===--- PassesFwd.h - Creation functions for LLVM passes -------*- C++ -*-===//
 //
 // This source file is part of the Swift.org open source project
 //

include/swift/SIL/PatternMatch.h

@@ -136,7 +136,7 @@ inline match_combine_and<LTy, RTy> m_CombineAnd(const LTy &L, const RTy &R) {
 
 /// Helper class to track the return type of vararg m_CombineOr matcher.
 template <typename ...Arguments>
-struct  OneOf_match;
+struct OneOf_match;
 
 template <typename T0>
 struct OneOf_match<T0> {
@@ -711,8 +711,8 @@ m_Ext(const T0 &Op0) {
 
 /// Matcher for any of the builtin CheckedTrunc instructions.
 template <typename T0>
-inline  typename OneOf_match<BuiltinApplyTy<T0>, BuiltinApplyTy<T0>,
-                             BuiltinApplyTy<T0>, BuiltinApplyTy<T0>>::Ty
+inline typename OneOf_match<BuiltinApplyTy<T0>, BuiltinApplyTy<T0>,
+                            BuiltinApplyTy<T0>, BuiltinApplyTy<T0>>::Ty
 m_CheckedTrunc(const T0 &Op0) {
   return m_UToSCheckedTrunc(Op0) || m_SToUCheckedTrunc(Op0) ||
          m_UToUCheckedTrunc(Op0) || m_SToSCheckedTrunc(Op0);