Vicente Mataix =?utf-8?q?Ferrándiz?= <vmat...@altair.com>,
Vicente Mataix =?utf-8?q?Ferrándiz?= <vmat...@altair.com>,
Vicente Mataix =?utf-8?q?Ferrándiz?= <vmat...@altair.com>
Message-ID:
In-Reply-To: <llvm.org/llvm/llvm-project/pull/127...@github.com>


================
@@ -446,6 +448,12 @@ async def main() -> None:
         action="store_true",
         help="Allow empty enabled checks.",
     )
+    parser.add_argument(
+        "-ignore-insert-conflict",
----------------
carlosgalvezp wrote:

Ok, then I see the following options:

- If possible, bump your installation to clang 15 (we are about to release 
clang 20, so it's fairly old ;) )
- Add a `-no-ignore-insert-conflict` option.
- Automatically check if the `clang_apply_replacements_binary` supports the 
`-ignore-insert-conflict` flag. You can easily do that by running the 
`clang-apply-replacements --help` command and checking if the output contains 
the flag. This is probably the most convenient option for the users since no 
changes to how the program is run are needed.

https://github.com/llvm/llvm-project/pull/127066
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to