- 26 10月, 2017 4 次提交
-
-
由 Heejae Chang 提交于
looks like I broke it when I did refactoring on KeepAliveSession by giving in wrong callback object. fix https://github.com/dotnet/roslyn/issues/22806 opened this for adding unit test - https://github.com/dotnet/roslyn/issues/22808 currently we don't have test around ISymbolSearchService.
-
由 Manish Vasani 提交于
-
由 AlekseyTs 提交于
Closes #7582.
-
由 Andy Gocke 提交于
-
- 25 10月, 2017 2 次提交
-
-
由 Manish Vasani 提交于
-
由 Manish Vasani 提交于
-
- 24 10月, 2017 4 次提交
-
-
由 AlekseyTs 提交于
1. Ensure correct syntax nodes and implicit state are used for IArgument nodes matching OmittedArgumentSyntax. Fixes #22486. 2. Ensure correct argument kind is associated with synthesized arguments within query expressions. Fixes #22066. 3. Ensure the invariant that “each syntax node has at most one corresponding explicit IOperation node” is met for all test scenarios we have at the moment. In order to achieve this the following changes are made: -mark some synthesized bound nodes as compiler generated. -for assignment statements, ensure that ISimpleAssignmentExpression and ICompoundAssignmentExpression nodes are marked as Implicit because they are sharing syntax node with containing IExpressionStatement and VB doesn’t have a concept of an assignment expression. -for throw statements, ensure that IThrowExpression node is marked as Implicit because it is sharing syntax node with containing IExpressionStatement and VB doesn’t have a concept of a throw expression. -for Add/RemoveHandler statements, ensure that IEventAssignmentExpression node is marked as Implicit because it is sharing syntax node with containing IExpressionStatement and VB doesn’t have a concept of an event assignment expression. -ensure that receivers for IPropertyReferenceExpression representing references to query range variables are marked as implicit. -ensure that IPropertyReferenceExpression and IParameterReferenceExpression nodes representing references to query range variables are associated with correct syntax nodes. -ensure that return statements and blocks in query lambdas are marked as implicit. -for IInterpolatedStringText node, ensure the underlying ILiteralExpression is marked as implicit because it is sharing syntax node with its parent.
-
由 AlekseyTs 提交于
Ensire that IOperation nodes representing param arrays and default values are properly marked as implicit. (#22758) Fixes #21451.
-
-
由 Tomáš Matoušek 提交于
* Update PDB converter to 1.1.0-beta1-62221-01 * Enable more conversion tests
-
- 21 10月, 2017 1 次提交
-
-
由 Manish Vasani 提交于
Address more feedback from design meeting and expose IOperation.IsExpression and IOperation.IsStatement properties
-
- 20 10月, 2017 15 次提交
-
-
由 Charles Stoner 提交于
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
Fixes a case where large projects repeatedly deserialized syntax trees, resulting in severe UI delays while typing.
-
由 Manish Vasani 提交于
Microsoft.CodeAnalysis.Semantics renamed to Microsoft.CodeAnalysis.Operations
-
由 Manish Vasani 提交于
-
由 Manish Vasani 提交于
-
由 Jason Malinowski 提交于
The use of Assert.True() is confusing as you end up with: Expected: [set] Actual: [another set] Expected: True Actual: False This dispenses of the second expected/actual.
-
由 Jason Malinowski 提交于
-
由 Manish Vasani 提交于
-
由 Manish Vasani 提交于
-
由 Manish Vasani 提交于
1. Rename -Expression and -Statement nodes to -Operation 2. Ensure all IOperation interfaces are suffixed with Operation 3. Rename all OperationKinds to match the corresponding IOperation interfaces without the prefix I and suffix Operation. Also fixed the operation ranges to be all contigous range. 4. Rename all the OperationVisitor methods to also match the corresponding IOperation interfaces without the prefix I and suffix Operation. 5. Merge the following interfaces which were semantically same, but syntactically different: 1. IInvalidExpression and IInvalidStatement merged to IInvalidOperation 2. IIfStatement and IConditionalExpression merged to IConditionalOperation 6. Update doc comments for all IOperation APIs to have 2 sections: 1. Summary section which cites pure semantics of the API without any mention of the language, expression/statement, current usage/implementation, etc. 2. Current usage para which cites how these APIs are used in current C# and VB implementation of these interfaces.
-
由 Charles Stoner 提交于
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
Before this, if we couldn't find the project we'd throw exceptions and possibly crash or do something bad.
-
由 Jason Malinowski 提交于
Holding onto Project directly meant the snapshot would be leaked. We should only hold onto the SymbolKey so we can resolve it later.
-
- 19 10月, 2017 4 次提交
-
-
由 Omar Tawfik 提交于
* Closes #18171 * ReadOnly Tuple Structs * Closes #18172
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
If a symbol couldn't be resolved, we would bail the search and never notify the UI that we stopped searching. We also wouldn't complete the IAsyncToken either. While I was here I also noticed that we were starting the async operation asynchronously which could have resulted in flakiness in integration tests. Our pattern is anything starting async work should start the operation right away, so we can confidently wait until the operation is complete. # Conflicts: # src/EditorFeatures/Core/Implementation/CallHierarchy/Finders/AbstractCallFinder.cs
-
由 Julien Couvreur 提交于
-
- 18 10月, 2017 5 次提交
-
-
由 Heejae Chang 提交于
* made children not to return null and reorder children in evaluation order * added some verification * fixed formatting * fixed ordering * removed temp variable.
-
由 Gen Lu 提交于
-
由 AlekseyTs 提交于
Fixes #22679. Fixes #7397. Related to #22029.
-
由 Gen Lu 提交于
-
由 AlekseyTs 提交于
Do not expose implicit IInstanceReferenceExpression in an IDelegateCreationExpression targeting static method. (#22706) Fixes #15513.
-
- 17 10月, 2017 5 次提交
-
-
由 Sam Harwell 提交于
Fixes #22723
-
由 Sam Harwell 提交于
Fixes #21021
-
由 Manish Vasani 提交于
-
由 Gen Lu 提交于
-
由 Manish Vasani 提交于
-