- 08 7月, 2017 1 次提交
- 07 7月, 2017 1 次提交
-
-
由 Manish Vasani 提交于
-
- 28 6月, 2017 1 次提交
-
-
由 Heejae Chang 提交于
-
- 22 6月, 2017 1 次提交
-
-
由 Manish Vasani 提交于
-
- 18 5月, 2017 1 次提交
-
-
由 Manish Vasani 提交于
Fixes #18300
-
- 16 5月, 2017 1 次提交
-
-
由 Heejae Chang 提交于
-
- 09 5月, 2017 1 次提交
-
-
由 Manish Vasani 提交于
-
- 06 5月, 2017 1 次提交
-
-
由 Manish Vasani 提交于
The current IOperation API implementation of BoundDelegateCreationExpression has a bunch of issues and needs to be redesigned. This is tracked by #8897 and will be addressed post 15.3. Meanwhile, to unblock analyzers on code containing delegate creation expressions with lambda arguments, this bound node has been switched to OperationKind.None with override for Children property. Fixes the first repro case provided in #8884
-
- 05 5月, 2017 1 次提交
-
-
由 Manish Vasani 提交于
There are couple of changes here: 1. API change: `ImmutableArray<ISymbolInitializer> MemberInitializers` is changed to `ImmutableArray<IOperation> Initializers`. 2. Implementation changes: 1. Instead of returning the member initializers as synthesized ISymbolInitializer nodes, we now return member intializers as IAssignmentExpression nodes. This ensures completeness of IOperation tree. 2. Now we also return the collection intializer expressions within an object creation expression. Fixes #18115 There are 2 bugs still affecting this area: 1. #18781: IOperation API shape for collection initializer expressions 2. #19276: Missing Field/Property reference expression nodes in object creation initializer node
-
- 03 5月, 2017 1 次提交
-
-
由 Manish Vasani 提交于
-
- 27 4月, 2017 1 次提交
-
-
由 Manish Vasani 提交于
-