[clang] [NFC] Fix clang format errors (PR #82721)

[via cfe-commits]

llvmbot wrote:


<!--LLVM PR SUMMARY COMMENT-->
@llvm/pr-subscribers-clang

@llvm/pr-subscribers-hlsl

Author: AtariDreams (AtariDreams)

<details>
<summary>Changes</summary>

These keep tripping up the build bots for clang and preventing testing on libc to go forward.

---
Full diff: https://github.com/llvm/llvm-project/pull/82721.diff


1 Files Affected:

- (modified) clang/docs/HLSL/ExpectedDifferences.rst (+2-2) 


``````````diff
diff --git a/clang/docs/HLSL/ExpectedDifferences.rst b/clang/docs/HLSL/ExpectedDifferences.rst
index 60001b22dc7920..d1b6010f10f43a 100644
--- a/clang/docs/HLSL/ExpectedDifferences.rst
+++ b/clang/docs/HLSL/ExpectedDifferences.rst
@@ -93,7 +93,7 @@ behavior between Clang and DXC. Some examples include:
     fma(X, Y, Z); // DXC: Fails to resolve no known conversion from float to double.
                   // Clang: Resolves to fma(double,double,double).
   #endif
-    
+
     double D = dot(A, B); // DXC: Resolves to dot(double3, double3), fails DXIL Validation.
                           // FXC: Expands to compute double dot product with fmul/fadd
                           // Clang: Resolves to dot(float3, float3), emits conversion warnings.
@@ -102,7 +102,7 @@ behavior between Clang and DXC. Some examples include:
 
 .. note::
 
-  In Clang, a conscious decision was made to exclude the ``dot(vector<double,N>, vector<double,N>)`` 
+  In Clang, a conscious decision was made to exclude the ``dot(vector<double,N>, vector<double,N>)``
   overload and allow overload resolution to resolve the
   ``vector<float,N>`` overload. This approach provides ``-Wconversion``
   diagnostic notifying the user of the conversion rather than silently altering

``````````

</details>


https://github.com/llvm/llvm-project/pull/82721