Merge pull request #9468 from microsoft/main

Merge for 1.11.0

Author: sean-mcmanus

Extension/CHANGELOG.md

@@ -1,61 +1,63 @@
 # C/C++ for Visual Studio Code Change Log
 
-## Version 1.10.4: June 3, 2022
+## Version 1.11.0: June 20, 2022
+### New Features
+* Add inlay hints for parameters and auto types. [#5845](https://github.com/microsoft/vscode-cpptools/issues/5845)
+
 ### Bug Fixes
-* Fix formatting issue with vcFormat when using multi-byte UTF-8 sequences. [#9297](https://github.com/microsoft/vscode-cpptools/issues/9297)
-* Add support for "user" level and "workspace" level debug configurations. [#9319](https://github.com/microsoft/vscode-cpptools/issues/9319)
-* Fix code analysis with g++ 12 system headers. [#9347](https://github.com/microsoft/vscode-cpptools/issues/9347)
-* Fix crash on macOS <= 10.14, due to missing symbol. [#9387](https://github.com/microsoft/vscode-cpptools/issues/9387)
+* Fix doxygen comments not being displayed for multiple adjacent `@brief` or `@return` tags. [#9316](https://github.com/microsoft/vscode-cpptools/issues/9316)
+* Fix crash if clang-tidy returns a replacement with an empty FilePath. [#9437](https://github.com/microsoft/vscode-cpptools/issues/9437)
+* Fix skipping the compiler argument after `-c`. [#9453](https://github.com/microsoft/vscode-cpptools/issues/9453)
+* Fix `-std:c++20` not being handled with cl.exe. [#9458](https://github.com/microsoft/vscode-cpptools/issues/9458)
 
-## Version 1.10.3: May 23, 2022
-### New Feature
-* Add code actions to apply clang-tidy fixes. [#8476](https://github.com/microsoft/vscode-cpptools/issues/8476)
-* Make the "Run and Debug" button feature available to all users. [#9306](https://github.com/microsoft/vscode-cpptools/issues/9306)
+## Version 1.10.7: June 15, 2022
+### Bug Fixes
+* Fix bugs with process creation on Windows (which caused IntelliSense to fail). [#9431](https://github.com/microsoft/vscode-cpptools/issues/9431)
 
+## Version 1.10.6: June 14, 2022
 ### Bug Fixes
-* Fix several IntelliSense bugs. [#6226](https://github.com/microsoft/vscode-cpptools/issues/6226), [#8294](https://github.com/microsoft/vscode-cpptools/issues/8294), [#8530](https://github.com/microsoft/vscode-cpptools/issues/8530), [#8725](https://github.com/microsoft/vscode-cpptools/issues/8725), [#8751](https://github.com/microsoft/vscode-cpptools/issues/8751), [#9076](https://github.com/microsoft/vscode-cpptools/issues/9076), [#9224](https://github.com/microsoft/vscode-cpptools/issues/9224), [#9336](https://github.com/microsoft/vscode-cpptools/issues/9336)
-* Prevent language service activation for macOS older than 10.12. [PR #9328](https://github.com/microsoft/vscode-cpptools/pull/9328)
+* Fix `@responseFile` in `compilerArgs` not being handled on Linux/Mac. [#9434](https://github.com/microsoft/vscode-cpptools/issues/9434)
+* Fix debug preLaunchTask not working when `C_Cpp.intelliSenseEngine` is `"Disabled"`. [#9446](https://github.com/microsoft/vscode-cpptools/issues/9446)
+* Make the `C_Cpp.legacyCompilerArgsBehavior` setting non-deprecated.
 
-## Version 1.10.2: May 12, 2022
-### Bug Fix
-* Fix abnormal process termination (causing core dump creation on some systems) during process creation on Linux/Mac. [#9301](https://github.com/microsoft/vscode-cpptools/issues/9301)
+## Version 1.10.5: June 8, 2022
+### New Features
+* Add code actions to apply clang-tidy fixes (and other actions). [#8476](https://github.com/microsoft/vscode-cpptools/issues/8476)
+* Added support for setting values on top level watch window expressions. [#9019](https://github.com/microsoft/vscode-cpptools/issues/9019)
+* Make the "Run and Debug" button feature available to all users. [#9306](https://github.com/microsoft/vscode-cpptools/issues/9306)
 
-## Version 1.10.1: May 10, 2022
 ### Enhancements
+* Add `C_Cpp.clangTidy.useBuildPath` setting to enable using `-p` with clang-tidy. [#8740](https://github.com/microsoft/vscode-cpptools/issues/8740), [#8952](https://github.com/microsoft/vscode-cpptools/issues/8952)
 * Generate launch.json when adding a new debug configuration. [#9100](https://github.com/microsoft/vscode-cpptools/issues/9100)
 * Prioritize the "folder" option when doing a `#include` completion. [#9222](https://github.com/microsoft/vscode-cpptools/issues/9222)
 * Add compiler path to debug configuration details. [PR #9264](https://github.com/microsoft/vscode-cpptools/pull/9264)
-
-### Bug Fixes
-* Fix handling of `@response` files for clang-tidy on Windows. [#8843](https://github.com/microsoft/vscode-cpptools/issues/8843),  [#9032](https://github.com/microsoft/vscode-cpptools/issues/9032), [#9102](https://github.com/microsoft/vscode-cpptools/issues/9102)
-* Fix cpptools-srv zombie processes. [#9261](https://github.com/microsoft/vscode-cpptools/issues/9261)
-* Fix `C_Cpp.codeAnalysis.clangTidy.useBuildPath` adding "compile_commands.json" to the `-p` argument. [#9273](https://github.com/microsoft/vscode-cpptools/issues/9273)
-* Fix Go to Definition on a `#include` with an absolute path. [#9287](https://github.com/microsoft/vscode-cpptools/issues/9287)
-
-## Version 1.10.0: April 21, 2022
-### New Feature
-* Added support for setting values on top-level watch window expressions. [#9019](https://github.com/microsoft/vscode-cpptools/issues/9019)
-
-### Enhancements
-* Add a `C_Cpp.clangTidy.useBuildPath` setting to enable using `-p` with clang-tidy. [#8740](https://github.com/microsoft/vscode-cpptools/issues/8740), [#8952](https://github.com/microsoft/vscode-cpptools/issues/8952)
 * Update the bundled clang-format and clang-tidy to version 14.0.0.
 
 ### Bug Fixes
-* Fix System.NullReferenceException when continuing after adding a breakpoint. [#1297](https://github.com/microsoft/MIEngine/issues/1297)
-* Fix an issue with shell processing incorrectly occurring for `arguments` fields in `compile_commands.json` files. [#8649](https://github.com/microsoft/vscode-cpptools/issues/8649)
+* Fix 'System.NullReferenceException when continuing after adding breakpoint.' [#1297](https://github.com/microsoft/MIEngine/issues/1297)
 * Fix completion not working in `#define` definitions and in definition names when manually invoked. [#4662](https://github.com/microsoft/vscode-cpptools/issues/4662), [#8973](https://github.com/microsoft/vscode-cpptools/issues/8973), [#9078](https://github.com/microsoft/vscode-cpptools/issues/9078)
-* Fix an issue with inconsistent handling of shell escaping in compiler arg fields. All compiler arg array fields are now assumed to not include shell quoting, escaping or shell variables. Added a `C_Cpp.legacyCompilerArgsBehavior` to restore the legacy behavior. [#8963](https://github.com/microsoft/vscode-cpptools/issues/8963)
+* Fix several IntelliSense bugs. [#6226](https://github.com/microsoft/vscode-cpptools/issues/6226), [#8294](https://github.com/microsoft/vscode-cpptools/issues/8294), [#8530](https://github.com/microsoft/vscode-cpptools/issues/8530), [#8725](https://github.com/microsoft/vscode-cpptools/issues/8725), [#8751](https://github.com/microsoft/vscode-cpptools/issues/8751), [#9076](https://github.com/microsoft/vscode-cpptools/issues/9076), [#9224](https://github.com/microsoft/vscode-cpptools/issues/9224), [#9336](https://github.com/microsoft/vscode-cpptools/issues/9336).
+* Fix issue with shell processing incorrectly occurring for `arguments` fields in `compile_commands.json` files. [#8649](https://github.com/microsoft/vscode-cpptools/issues/8649)
+* Fix handling of `@response` files for clang-tidy on Windows. [#8843](https://github.com/microsoft/vscode-cpptools/issues/8843),  [#9032](https://github.com/microsoft/vscode-cpptools/issues/9032), [#9102](https://github.com/microsoft/vscode-cpptools/issues/9102)
+* Fix issue with inconsistent handling of shell escaping in compiler arg fields.  All compiler arg array fields are now assumed to not include shell quoting, escaping or shell variables. Added a `C_Cpp.legacyCompilerArgsBehavior` to restore the legacy behavior. [#8963](https://github.com/microsoft/vscode-cpptools/issues/8963)
 * Add localized strings for build tasks. [#9051](https://github.com/microsoft/vscode-cpptools/issues/9051)
 * Fix Go to Definition with C for identifiers that are C++ keywords. [#9081](https://github.com/microsoft/vscode-cpptools/issues/9081)
 * Fix the new Run/Debug Code button not working with a modified program location. [#9082](https://github.com/microsoft/vscode-cpptools/issues/9082)
 * Fix `__GNUC__` system defines causing clang-tidy to undefine `_Float32`. [#9091](https://github.com/microsoft/vscode-cpptools/issues/9091)
-* Fix breakpoints set before launch in shared objects cannot be disabled/deleted. [#9095](https://github.com/microsoft/vscode-cpptools/issues/9095)
+* Fix 'breakpoints set before launch in shared objects cannot be disabled/deleted' [#9095]([https://github.com/microsoft/vscode-cpptools/issues/9095)
 * Fix compiler querying failing for compilers that don't output system includes. [#9099](https://github.com/microsoft/vscode-cpptools/issues/9099)
 * Fix completion occurring (when it shouldn't) after the comma in a definition list. [#9101](https://github.com/microsoft/vscode-cpptools/issues/9101)
 * Fix `;` incorrectly matching for `break;` and `continue;` completion. [#9115](https://github.com/microsoft/vscode-cpptools/issues/9115)
+* Fix Go to Definition on a `#include` with an absolute path. [#9287](https://github.com/microsoft/vscode-cpptools/issues/9287)
+* Fix formatting issue with vcFormat when using multi-byte UTF-8 sequences. [#9297](https://github.com/microsoft/vscode-cpptools/issues/9297)
+* Fix language server disabling due to a TypeError when invalid json values are used. [#9302](https://github.com/microsoft/vscode-cpptools/issues/9302)
+* Add support for "user" level and "workspace" level debug configurations. [#9319](https://github.com/microsoft/vscode-cpptools/issues/9319)
+* Prevent language service activation for macOS older than 10.12. [PR #9328](https://github.com/microsoft/vscode-cpptools/pull/9328)
+* Fix code analysis with g++ 12 system headers. [#9347](https://github.com/microsoft/vscode-cpptools/issues/9347)
+* Enable correct symbol parsing for methods that call loop-like macros without requiring the macro be added to cpp.hint. [#9378](https://github.com/microsoft/vscode-cpptools/issues/9378)
+* Fix a code analysis error when C++23 is used. [#9404](https://github.com/microsoft/vscode-cpptools/issues/9404)
 * Fix a potential crash in cpptools (in `get_identifier_at_offset`).
 * Other Run and Debug button updates/fixes.
-* IntelliSense parsing fixes.
 
 ## Version 1.9.8: April 20, 2022
 ### Bug Fixes

Extension/bin/messages/cs/messages.json

@@ -3457,5 +3457,9 @@
   "znaková konstanta UTF-16 nemůže zabírat více než jednu jednotku kódu; hodnota byla zkrácena",
   "oba argumenty musí mít stejný typ",
   "typ %t není platný jako argument pro tento předdefinovan.",
-  "voláno z %nd:"
+  "voláno z %nd:",
+  "kvalifikovaný typ je pro anonymní bitová pole nestandardní.",
+  "typ elementu vektorové podmínky (%t1) musí mít stejnou velikost jako typ elementu výsledku (%t2).",
+  "typ operandu vektoru s plovoucí desetinnou čárkou (%t) nemá žádný odpovídající celočíselný vektorový typ.",
+  "mangling pro výrazy requires ještě není implementovaný."
 ]

Extension/bin/messages/de/messages.json

@@ -3457,5 +3457,9 @@
   "Eine UTF-16-Zeichenkonstante darf nicht mehrere Codeeinheiten belegen. Wert abgeschnitten.",
   "Beide Argumente müssen denselben Typ aufweisen.",
   "Der Typ \"%t\" ist als Argument für dieses integrierte Element ungültig.",
-  "aufgerufen von %nd:"
+  "aufgerufen von %nd:",
+  "ein qualifizierter Typ ist kein Standard für anonyme Bitfelder",
+  "der Elementtyp der Vektorbedingung (%t1) muss dieselbe Größe haben wie der Elementtyp des Ergebnisses (%t2)",
+  "der Gleitkomma-Vektoroperandentyp (%t) hat keinen übereinstimmenden ganzzahligen Vektortyp",
+  "das Mangling für 'requires'-Ausdrücke ist noch nicht implementiert"
 ]

Extension/bin/messages/es/messages.json

@@ -3457,5 +3457,9 @@
   "una constante de caracteres UTF-16 no puede ocupar más de una unidad de código; valor truncado",
   "ambos argumentos deben tener el mismo tipo",
   "el tipo %t no es válido como argumento para este elemento integrado",
-  "llamado desde %nd:"
+  "llamado desde %nd:",
+  "un tipo calificado no es estándar para campos de bits anónimos",
+  "el tipo de elemento de la condición de vector (%t1) debe tener el mismo tamaño que el tipo de elemento del resultado (%t2)",
+  "el tipo de operando de vector de punto flotante (%t) no tiene ningún tipo de vector entero coincidente",
+  "aún no se ha implementado la limpieza de expresiones \"requires\""
 ]

Extension/bin/messages/fr/messages.json

@@ -3457,5 +3457,9 @@
   "une constante de caractères UTF-16 ne peut pas occuper plusieurs unités de code ; valeur tronquée",
   "les deux arguments doivent avoir le même type",
   "le type %t n’est pas valide en tant qu’argument pour ce builtin",
-  "appelé à partir de %nd :"
+  "appelé à partir de %nd :",
+  "un type qualifié n’est pas standard pour les champs de bits anonymes.",
+  "le type d’élément de la condition vectorielle (%t1) doit avoir la même taille que le type d’élément du résultat (%t2).",
+  "le type d’opérande vectoriel à virgule flottante (%t) n’a pas de type de vecteur entier correspondant.",
+  "La gestion des expressions \"requires\" n'est pas encore implémentée."
 ]

Extension/bin/messages/it/messages.json

@@ -3457,5 +3457,9 @@
   "una costante di caratteri UTF-16 non può occupare più di un'unità di codice; valore troncato",
   "entrambi gli argomenti devono avere lo stesso tipo",
   "il tipo %t non è valido come argomento per questa compilazione",
-  "chiamato da %nd:"
+  "chiamato da %nd:",
+  "un tipo qualificato non è conforme allo standard per i campi di bit anonimi",
+  "il tipo di elemento della condizione vettoriale (%t1) deve avere le stesse dimensioni del tipo di elemento del risultato (%t2)",
+  "il tipo di operando di vettore a virgola mobile (%t) non ha un tipo di vettore intero corrispondente",
+  "il mangling per le espressioni 'requires' non è ancora implementato"
 ]

Extension/bin/messages/ja/messages.json

@@ -3457,5 +3457,9 @@
   "UTF-16 文字定数は複数のコード単位を占有できません。値が切り捨てられました",
   "両方の引数は同じ型である必要があります",
   "型 %t は、このビルトインの引数として無効です",
-  "%nd からの呼び出し:"
+  "%nd からの呼び出し:",
+  "修飾された型は匿名ビット フィールドでは非標準です",
+  "ベクトル条件 (%t1) の要素型は、結果の要素型 (%t2) と同じサイズである必要があります",
+  "浮動小数点ベクトル オペランド型 (%t) に一致する整数ベクトル型がありません",
+  "'requires' 式のためのマングリングは、まだ実装されていません"
 ]

Extension/bin/messages/ko/messages.json

@@ -3457,5 +3457,9 @@
   "UTF-16 문자 상수는 코드 단위를 두 개 이상 사용할 수 없음; 값 잘림",
   "두 인수의 형식이 같아야 함",
   "%t 형식은 이 기본 제공의 인수로 사용할 수 없음",
-  "%nd에서 호출"
+  "%nd에서 호출",
+  "정규화된 형식이 익명 비트 필드에 대해 표준이 아닙니다.",
+  "벡터 조건의 요소 유형(%t1)은 결과의 요소 유형(%t2)과 크기가 같아야 합니다.",
+  "부동 소수점 벡터 피연산자 유형(%t)에 일치하는 정수 벡터 유형이 없습니다.",
+  "'requires' 식에 대한 mangling이 아직 구현되지 않았습니다."
 ]

Extension/bin/messages/pl/messages.json

@@ -3457,5 +3457,9 @@
   "stała znaków UTF-16 nie może zajmować więcej niż jednej jednostki kodu; obcięta wartość",
   "oba argumenty muszą mieć ten sam typ",
   "typ %t jest nieprawidłowy jako argument dla tej wbudowanej",
-  "wywołano z %nd:"
+  "wywołano z %nd:",
+  "kwalifikowany typ jest niestandardowy dla anonimowych pól bitowych",
+  "typ elementu warunku wektora (%t1) musi mieć taki sam rozmiar jak typ elementu wyniku (%t2)",
+  "typ operandu wektora zmiennoprzecinkowego (%t) nie ma zgodnego typu wektora liczb całkowitych",
+  "nie jest jeszcze zaimplementowane dekorowanie wyrażeń typu „requires”."
 ]

Extension/bin/messages/pt-br/messages.json

@@ -3457,5 +3457,9 @@
   "uma constante de caractere UTF-16 não pode ocupar mais de uma unidade de código; valor truncado",
   "ambos os argumentos devem ter o mesmo tipo",
   "o tipo %téinválido como argumento para este builtin",
-  "chamado de %nd:"
+  "chamado de %nd:",
+  "um tipo qualificado não é padrão para campos de bits anônimos",
+  "o tipo de elemento da condição de vetor (%t1) deve ter o mesmo tamanho que o tipo de elemento do resultado (%t2)",
+  "o tipo de operando vetorial de ponto flutuante (%t) não tem nenhum tipo de vetor inteiro correspondente",
+  "a estruturação para expressões 'requires' ainda não foi implementada"
 ]