- 18 11月, 2017 12 次提交
-
-
由 Heejae Chang 提交于
when OOP is killed by users, default(DesignerAttributeResult) is returned. it was okay when it was class, but not it being struct, it cause issue because NotApplicable return false rather than true in error case. so, change NotApplicable to Applicable so that it can handle the error case better.
-
由 Shyam N 提交于
Mop up merge of post-dev15.5-contrib to master
-
由 Tomáš Matoušek 提交于
Workaround for test SDK issue Microsoft/vstest#373
-
由 Sam Harwell 提交于
Disabled cross function inlining if used the same type parameter name.
-
由 Sam Harwell 提交于
Fixed generating delegate constructor
-
由 Sam Harwell 提交于
Look for type check in local declaration and return statements
-
由 Heejae Chang 提交于
* made NFW to use runtime callstack rather than callstack from fake exception also, made WatsonReporter from VS and ServiceHub to share more implementation * PR feedback. rather than using null exception which is taken cared by NFW, we explicitly throw exception to have callstack so that it can show up in perfview as well. * centralize who throws exception if given exception is never thrown. also, explicitly add runtime callstack in one of reserved slot to make NFW bucketting better. * fixed tests and added empty callstack test
-
由 Jared Parsons 提交于
Publishing to blob storage
-
-
由 Sam Harwell 提交于
-
由 Jason Malinowski 提交于
Merge post-dev15.5-contrib to master
-
由 Charles Stoner 提交于
Merge misc. changes for embedded attributes from 7a0467ec
-
- 17 11月, 2017 15 次提交
-
-
由 Alireza Habibi 提交于
-
由 Vladimir Sadov 提交于
Fixes an issue with flow analysis where branches within `try` could be considered as going through `finally`
-
由 Charles Stoner 提交于
Use synthesized attribute infrastructure for System.NullableAttribute Misc. Misc. Misc. Misc. Misc. Misc. PR feedback Override in PEMethodSymbol
-
由 Shyam N 提交于
Merge master to post-dev15.5-contrib
-
由 Ashley Hauck 提交于
Create build.sh
-
由 Vladimir Sadov 提交于
Reuse proxy fields in async state machine
-
由 Omar Tawfik 提交于
* Marshalling methods with `in` parameters should have [In] attribute * Apply [In] on all `in` parameters * More tests * nit
-
由 Andy Gocke 提交于
Also skip another test that failed while skipping the original test
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
由 Jared Parsons 提交于
-
- 16 11月, 2017 9 次提交
-
-
由 vsadov 提交于
-
由 vsadov 提交于
-
由 David Poeschl 提交于
Ensure CodeModel adds elastic trivia when setting names
-
由 Andy Gocke 提交于
Currently, full signing is always disabled on Linux/Mac because it was not supported. Now, it is supported. To avoid taking a dependency on full signing, this only enables full signing when we're confirmed to be building with a bootstrap compiler.
-
由 AlekseyTs 提交于
Fix NullReferenceException thrown while building IOperation node for dynamic object member initializer. (#23162) Fixes #23154.
-
由 AlekseyTs 提交于
Related to #22548 and #22229.
-
由 Manish Vasani 提交于
Do not expose operation nodes for BoundRangeVariables in C# query exp…
-
由 AlekseyTs 提交于
Related to #22548 and #22229. There are several issues with IOperation tree when it comes to conversions applied to tuple literals: 1. When conversion is explicitly specified in code, it is translated to conversions on individual elements of the literal and these BoundConversion nodes are also marked as explicitly specified in code (which makes sense). However, the syntax associated with a BoundConversion node on top of an element matches the syntax of the element (which also makes sense). The problem is that both the conversion node and the element appear as “explicit” in IOperation tree, which violates one of the tree invariants – at most one “explicit” node for a given syntax node. 2. When a tuple literal is converted, compiler creates a BoundConvertedTupleLiteral node, which has the target tuple type as its Type, but the BoundConversion node on top of the BoundConvertedTupleLiteral captures conversion information (kind, etc.) for conversion From tuple’s natural type to the target type. So, often, we end up with both nodes having The same Type, but the conversion says it is not an identity conversion. This shape helps SemanticModel to provide accurate information about types and conversions, but the IOperation tree looks very confusing. 3. When conversion is explicitly specified in code, the BoundConversion node from the previous item is marked as explicitly specified in code, but it shares syntax node with BoundConvertedTupleLiteral. Both nodes appear as “explicit” in IOperation tree, which violates the same invariant. 4. When conversion is explicitly specified in code, compiler adds yet another explicit Identity conversion on top of the BoundConversion node from the previous item. It is needed for proper SemanticModel behavior. Even when it uses different syntax, the IOperation tree looks very confusing, there are two conversions on top of each other and it is not clear why intermediate conversion node is needed. In order to address all these issue the following changes are made to IOperation factory: - If conversion node is associated with the same syntax as its operand, the conversion is marked as isImplicit. - If Type of BoundConvertedTupleLiteral matches the Type of BoundConversion node on top of it the conversion node is not added to the IOperation tree. Instead a new property is added to ITupleOperation interface, called NaturalType. The property exposes the natural type of the tuple literal and makes it easy for consumers to figure out if a conversion from a natural type of a tuple literal took place. - If Type of BoundConvertedTupleLiteral doesn’t match the Type of BoundConversion node on top of it and there is an identity conversion node on top of the BoundConversion node, the intermediate conversion node is not added to the IOperation tree, its conversion information is used for the top-most conversion node (instead of saying that it is identity).
-
由 khyperia 提交于
-
- 15 11月, 2017 4 次提交
-
-
由 Ashley Hauck 提交于
Reduce the use of the preprocessor
-
由 vsadov 提交于
Fixes an issue with flow analysis where branches within `try` could be considered as going through `finally` We could incorrectly assume that variable is assigned (or unassigned in async capture tracking case). As a resutl we could - allow use of unassigned locals (undefined behavior) - not capture a local whose value survives `await` (NRE crash) Also added a regression test fro VB, which does not seem affected. Fixes:#19831
-
由 Julien Couvreur 提交于
-
由 Julien Couvreur 提交于
-