[libcxx-commits] [libcxx] [libcxxabi] [libcxx] [test] Detect the UCRT printf("%a") formatting bug (PR #99846)

[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 56ad7cc0126f9899fd884391cfa10b6359206c01...4b0be46ab728d3285b41be5e2a2720d2970f2eb4 libcxx/utils/libcxx/test/features.py
``````````

</details>

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

``````````diff
--- features.py	2024-07-22 08:29:59.000000 +0000
+++ features.py	2024-07-22 08:35:36.712581 +0000
@@ -266,12 +266,12 @@
     # Check for a Windows UCRT bug (not fixed upstream yet).
     # With UCRT, printf("%a", 0.0) produces "0x0.0000000000000p+0",
     # while other C runtimes produce just "0x0p+0".
     # https://developercommunity.visualstudio.com/t/Printf-formatting-of-float-as-hex-prints/1660844
     Feature(
-        name='win32-broken-printf-a-precision',
-        when=lambda cfg: '_WIN32' in compilerMacros(cfg)
+        name="win32-broken-printf-a-precision",
+        when=lambda cfg: "_WIN32" in compilerMacros(cfg)
         and not programSucceeds(
             cfg,
             """
             #include <stdio.h>
             #include <string.h>

``````````

</details>


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