- 15 11月, 2019 1 次提交
-
-
由 Allison Chou 提交于
-
- 13 11月, 2019 2 次提交
-
-
由 Julien Couvreur 提交于
* Implement lambda discard parameters * Remove duplicate tests * Factor logic to recognize underscore tokens * Align symbol display with other discards * Distinguish discards in QuickInfo * Add IsDiscard property instead of IDiscardSymbol * Adjust IDE logic to use IsDiscard * Avoid large tuple return * Add test for ref/out discard parameters * Address PR feedback and test plan ideas * Allow in expression trees * Support general discard parameters * Add IDE tests * Emit with unspeakable name * Remove unused error code * Only support lambdas * Fix tests * Address some PR feedback * Address remaining feedback * Address more feedback * Fix conflict * Update PublicAPI.Unshipped.txt * Update PublicAPI.Unshipped.txt * Add ChangeSignature tests * Add SymbolCompletion tests * Add InlineRename test * Typo
-
由 Allison Chou 提交于
-
- 11 11月, 2019 2 次提交
-
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
- 09 11月, 2019 1 次提交
-
-
由 Allison Chou 提交于
-
- 02 11月, 2019 1 次提交
-
-
由 Allison Chou 提交于
-
- 05 10月, 2019 1 次提交
-
-
由 Tomáš Matoušek 提交于
* Remove BaseSolution property * Refactor GetAllAddedSymbolsAsync * Track documents that do not match the debuggee * Handle design-time-only documents and documents with no sequence points
-
- 02 10月, 2019 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 01 10月, 2019 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 20 9月, 2019 1 次提交
-
-
由 nnpcYvIVl 提交于
-
- 14 9月, 2019 1 次提交
-
-
由 Gen Lu 提交于
-
- 11 9月, 2019 1 次提交
-
-
由 Cheryl Borley 提交于
-
- 30 8月, 2019 1 次提交
-
-
- 22 8月, 2019 1 次提交
-
- 17 8月, 2019 1 次提交
-
-
由 Gen Lu 提交于
-
- 15 8月, 2019 1 次提交
-
-
由 Lavanya 提交于
-
- 09 8月, 2019 2 次提交
- 27 7月, 2019 1 次提交
-
-
由 Tomáš Matoušek 提交于
* Report rude edits when updating method containing switch expression. Fix stackalloc rude edits. * Updating modifiers of local functions * await foreach, await using * Improve error message * Distinguish async foreach/using from synchronous in error messages * Using declaration * Report rude edit when editing using statement/declaration around non-leaf AS * Rude edits for switch with patterns * Fix VB issues with active statements in nested single-line functions and when updating iterators * Update comment * Fix duplicate rude edit
-
- 25 7月, 2019 1 次提交
-
-
由 Pär Björklund 提交于
If it's written to a warning annotation is displayed in the refactoring window to warn that semantics may change.
-
- 16 7月, 2019 1 次提交
-
-
由 Tomáš Matoušek 提交于
* Emit tests * Report rude edits for unsupported DIM operations * Allow EnC tests to specify TFMs to build against * EnC: test against netcoreapp30 * Test fixes * Fix merge
-
- 13 7月, 2019 1 次提交
-
-
由 Tomáš Matoušek 提交于
* Top-level types enumeration refactoring * Simplify DefinitionMap * Include namespaces in synthesized definition map * Add SynthesizedNamespaceSymbol * Embedded Attributes * Test synthesized attributes * Clean up EnC tests * Clean up symbol matcher tests * Ref readonly return type, in parameter symbol matching tests * Enable using ref readonly returns, in parameters, ref structs during debugging * More tests * ReadOnly struct members * Fix langauge version mismatch * Merge fix ups * Feedback, skip tests
-
- 12 7月, 2019 1 次提交
-
-
由 t-shzach 提交于
-
- 10 7月, 2019 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 28 6月, 2019 1 次提交
-
-
由 Tomáš Matoušek 提交于
-
- 24 6月, 2019 1 次提交
-
-
- 21 6月, 2019 1 次提交
-
-
- 15 6月, 2019 1 次提交
-
-
由 Tom Meschter 提交于
The resource in question has an ID that is 414 characters long. This is apparently too long for some of the tools used by the loc team, blocking parts of their processes. The exact failure mechanism is not well understood but in order to avoid problems with the final loc pass for 16.2 I'm just going to go ahead and shorten it. Unfortunately no one knows how long resource IDs can be before they cause problems. At the suggestion of the loc team I'm shortening this one by 50 characters which lines up nicely with a natural break in the ID.
-
- 05 6月, 2019 1 次提交
-
-
由 Manish Vasani 提交于
We support configuration for boolean and enum based code style option values. The only unsupported current code style option from this fixer is specification of modifiers order, which is a custom user supplied string.
-
- 01 6月, 2019 1 次提交
-
-
由 Manish Vasani 提交于
(DisposableFieldsShouldBeDisposed) We will now flag disposable creations in methods that do not escape the method body (return value, out/ref params, assign to field/property, add to collection, etc.). Additionally, we also flag disposable fields of disposable types that are not disposed in the type's Dispose method. Ported analyzers share the core dataflow analysis computation with the analyzers in the roslyn-analyzers repo (Microsoft.CodeAnalysis.FlowAnalysis.Utilities). This PR does not add any code fixes. We already have a code refactoring that offers wrapping a disposable creation within a using statement. I am hoping to extend that to handle more cases and also possibly convert it to a code fix in follow-up PR(s).
-
- 23 5月, 2019 1 次提交
-
-
由 Manish Vasani 提交于
Add Configure severity code action to enable configuring severity of diagnostics using .editorconfig files (analyzer config documents)
-
- 18 5月, 2019 1 次提交
-
-
由 Tomáš Matoušek 提交于
* Revert "Revert "Make compilation outputs available via a workspace service (#34809)"" This reverts commit f4892bc4. * Handle non-absolute path set by VB Web App IntelliSense project
-
- 13 5月, 2019 1 次提交
-
-
由 David Poeschl 提交于
This reverts commit 3bdbd560.
-
- 11 5月, 2019 1 次提交
-
-
由 David Poeschl 提交于
This reverts commit 3bdbd560.
-
- 10 5月, 2019 1 次提交
-
-
由 Mirek Driml (Moravia IT) 提交于
-
- 09 5月, 2019 1 次提交
-
-
由 David Poeschl 提交于
This reverts commit 3bdbd560.
-
- 07 5月, 2019 2 次提交
-
-
由 yair halberstadt 提交于
-
由 yair halberstadt 提交于
-
- 03 5月, 2019 1 次提交
-
-
由 Manish Vasani 提交于
Fixes #35203 1. Improve the message for unused value assignment diagnostic to make it clear that we are flagging an unnecessary assignment, not an unused variable 2. Add descriptions for unused value assignment and unused parameter diagnostics to allow users to specify special discard symbol names that are respected by the analyzer. There are various cases where user wants to retain unused parameters (signature compat, documentation) and unnecessary assignments to locals (ease of debugging), but do not want to blanket suppress these diagnostics.
-