[libcxx-commits] [libcxx] [libc++] Optimize standard streams with sync_with_stdio(false) (PR #209161)

[via libcxx-commits]

github-actions[bot] wrote:

<!--LLVM CODE FORMAT COMMENT: {darker}-->


:warning: Python code formatter, darker found issues in your code. :warning:

<details>
<summary>
You can test this locally with the following command:
</summary>

``````````bash
darker --check --diff -r origin/main...HEAD libcxx/utils/libcxx/test/features/availability.py
``````````

:warning:
The reproduction instructions above might return results for more than one PR
in a stack if you are using a stacked PR workflow. You can limit the results by
changing `origin/main` to the base branch/commit you want to compare against.
:warning:

</details>

<details>
<summary>
View the diff from darker here.
</summary>

``````````diff
--- availability.py	2026-07-22 12:02:57.000000 +0000
+++ availability.py	2026-07-22 12:04:31.486237 +0000
@@ -133,11 +133,25 @@
 # For example, tests for availability markup should be expected to produce diagnostics
 # regardless of whether we're running against a system library, as long as we're using
 # a libc++ flavor that enables availability markup. Similarly, a test could fail when
 # run against the system library of an older version of FreeBSD, even though FreeBSD
 # doesn't provide availability markup at the time of writing this.
-for version in ("12", "13", "14", "15", "16", "17", "18", "19", "20", "21", "22", "23", "24"):
+for version in (
+    "12",
+    "13",
+    "14",
+    "15",
+    "16",
+    "17",
+    "18",
+    "19",
+    "20",
+    "21",
+    "22",
+    "23",
+    "24",
+):
     features.append(
         Feature(
             name="using-built-library-before-llvm-{}".format(version),
             when=lambda cfg, v=version: BooleanExpression.evaluate(
                 "stdlib=system && !_target-has-llvm-{}".format(v),

``````````

</details>


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