- 21 7月, 2016 1 次提交
-
-
由 Julien 提交于
-
- 24 6月, 2016 3 次提交
- 23 6月, 2016 1 次提交
-
-
由 AlekseyTs 提交于
Adjust various places outside of compiler to account for the fact that ArgumentSyntax.Expression can be null. Fixes #12147.
-
- 19 6月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 01 6月, 2016 2 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 26 5月, 2016 1 次提交
-
-
由 Brett V. Forsgren 提交于
-
- 07 5月, 2016 1 次提交
-
-
由 Julien 提交于
-
- 30 3月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 27 2月, 2016 1 次提交
-
-
由 Brett V. Forsgren 提交于
-
- 26 1月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 17 12月, 2015 1 次提交
-
-
由 Jason Malinowski 提交于
These tests were all using WpfFact, but not actually doing anything that required either WPF or an STA thread. We plan to enable parallelization of Facts (but not WpfFacts), and this ensures we can parallelize as many tests as possible.
-
- 30 11月, 2015 2 次提交
-
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
- 21 11月, 2015 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 20 11月, 2015 1 次提交
-
-
由 Jonathon Marolf 提交于
-
- 18 11月, 2015 1 次提交
-
-
由 Jonathon Marolf 提交于
-
- 11 11月, 2015 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 10 11月, 2015 1 次提交
-
-
由 Cyrus Najmabadi 提交于
Offer 'generate constructor' when a derived type doesn't include a delegating constructor to it's base type
-
- 16 10月, 2015 1 次提交
-
-
由 Paul Harrington 提交于
-
- 10 10月, 2015 1 次提交
-
-
由 Tanner Gooding 提交于
-
- 05 10月, 2015 1 次提交
-
-
由 Cyrus Najmabadi 提交于
Generate constructor had a logic bug causing it to consider any single constructor in an abstract base class to be an acceptable base-class-constructor for it to delegate to. This was the case, regardless of what the actual parameter types of that constructor were. Now we actually consider the parameter types in this case and only allow delegation if the parameter types would be assignable.
-
- 27 4月, 2015 1 次提交
-
-
由 Jonathon Marolf 提交于
The compiler does not generate semantic errors inside lambdas in the presence of syntactic errors causing several features to not work in lambdas with syntax errors. The bug for this ([1867](https://github.com/dotnet/roslyn/issues/1867)) was moved to milestone 1.1 so we are going to use an analyzer in the interim for 1.0. 1. We now check for IncompleteMemberSyntax nodes and LambdaExpressionSyntax nodes which contain syntax diagnostics on any of their descendant nodes. 2. We report both unbound identifier names and constructors that the compiler reports as binding, but which fail overload resolution (actually don't exist). Performance considerations should be mitigated by only doing these checks only lambdas with syntax errors. Other notes: - Renamed analyzer to UnboundIdentifier instead of AddImport since it is being used in more places than just the AddImport fixer - Updated the DiagnosticDescriptor for this analyzer to take localizeable strings. Fixes #1744 Fixes #1241 Fixes #1239
-
- 29 1月, 2015 1 次提交
-
-
由 beep boop 提交于
-