- 09 11月, 2017 3 次提交
-
-
由 Fredric Silberberg 提交于
-
由 Manish Vasani 提交于
* Ensure that we track additional member symbols in the VB binder context and populate the additional field/property symbols initialized by VB AsNew clause that initializes more than one field/property Note: This change also includes an API change to `IPropertyInitializer` as VB WithEvents declaration with AsNew clause initializer can initialize multiple properties. Fixes #17813 * Fix wording in some comments * Address review feedback * Fix build break
-
由 Fredric Silberberg 提交于
-
- 08 11月, 2017 5 次提交
-
-
由 Fredric Silberberg 提交于
-
由 Fredric Silberberg 提交于
-
由 AlekseyTs 提交于
Fixes #23004. Fixes #23009. Related to #22548 and #22229.
-
由 Manish Vasani 提交于
-
由 Manish Vasani 提交于
This change is now just a test-only change that verifies the current behavior.
-
- 07 11月, 2017 3 次提交
-
-
由 Fredric Silberberg 提交于
Don't print IgnoredArguments unless nonempty, added verification of Children property, addressed minor feedback items.
-
由 Fredric Silberberg 提交于
-
由 Manish Vasani 提交于
-
- 04 11月, 2017 2 次提交
-
-
由 AlekseyTs 提交于
Add IsRef property to IConditionalOperation and ISimpleAssignmentOperation, add RefKind property to ILocalSymbol. (#22933) Closes #21311.
-
由 Fredric Silberberg 提交于
-
- 02 11月, 2017 1 次提交
-
-
由 Manish Vasani 提交于
Fixes #22960
-
- 01 11月, 2017 2 次提交
- 31 10月, 2017 4 次提交
-
-
由 Gen Lu 提交于
-
由 AlekseyTs 提交于
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. (#22894) Related to #22229. The following changes are made: - Mark some synthesized bound nodes as compiler generated. - Use correct syntax for a tuple on the left hand side of deconstruction. - For throw statements, no longer add IExpressionStatementOperation on top of IThrowOperation node. - For IInterpolatedStringText node, ensure the underlying ILiteralExpression is marked as implicit because it is sharing syntax node with its parent.
-
由 Manish Vasani 提交于
-
由 Manish Vasani 提交于
Previously, we used to return two different operation blocks for the statements node within the body and the end block statement. This was incorrect, and was exposed when we recently started marking the implicit return statement in the sub as IsImplicit, and ended up with no explicit operations for an empty method body.
-
- 28 10月, 2017 2 次提交
-
-
由 Fredric Silberberg 提交于
Refactor ISingle and IMulti to IVariableDeclarator and IVariableDeclaration, to match syntax terms and be less confusing.
-
由 Fredric Silberberg 提交于
-
- 26 10月, 2017 2 次提交
-
-
由 Fredric Silberberg 提交于
-
由 Manish Vasani 提交于
This matches the VB behavior and avoids GetOperation returning null for parenthesized expression. Fixes #22751
-
- 25 10月, 2017 2 次提交
-
-
由 Fredric Silberberg 提交于
-
由 Manish Vasani 提交于
-
- 24 10月, 2017 2 次提交
-
-
由 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.
-
由 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 3 次提交
-
-
由 Manish Vasani 提交于
Microsoft.CodeAnalysis.Semantics renamed to Microsoft.CodeAnalysis.Operations
-
由 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.
-
由 Manish Vasani 提交于
-
- 18 10月, 2017 2 次提交
-
-
由 Heejae Chang 提交于
* made children not to return null and reorder children in evaluation order * added some verification * fixed formatting * fixed ordering * removed temp variable.
-
由 AlekseyTs 提交于
Do not expose implicit IInstanceReferenceExpression in an IDelegateCreationExpression targeting static method. (#22706) Fixes #15513.
-
- 17 10月, 2017 1 次提交
-
-
由 Manish Vasani 提交于
Addresses Preview and Documentation items from #22719
-
- 14 10月, 2017 1 次提交
-
-
由 Manish Vasani 提交于
-
- 11 10月, 2017 1 次提交
-
-
由 Fredric Silberberg 提交于
-
- 10 10月, 2017 1 次提交
-
-
由 Fredric Silberberg 提交于
-
- 09 10月, 2017 2 次提交
-
-
由 Manish Vasani 提交于
-
由 Manish Vasani 提交于
-