- 30 6月, 2020 1 次提交
-
-
由 Paul M Cohen 提交于
-
- 27 6月, 2020 1 次提交
-
-
由 Paul M Cohen 提交于
-
- 25 6月, 2020 3 次提交
-
-
由 Paul M Cohen 提交于
-
由 Paul M Cohen 提交于
-
由 Paul M Cohen 提交于
-
- 30 3月, 2020 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 06 3月, 2020 1 次提交
-
-
由 Manish Vasani 提交于
-
- 27 2月, 2020 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 23 1月, 2020 1 次提交
-
-
由 Jonathon Marolf 提交于
-
- 06 2月, 2019 1 次提交
-
-
由 David Barbet 提交于
-
- 30 1月, 2019 1 次提交
-
-
由 David Barbet 提交于
-
- 11 1月, 2019 1 次提交
-
-
由 David Barbet 提交于
-
- 11 8月, 2018 1 次提交
-
-
由 Joey Robichaud 提交于
The AbstractSpeculationAnalyzer would check whether casting symbols used in Invocable expressions would break semantics. However it was not considering all MemberAccess to be potentially invokable. This Changes the IsInvokable check to consider all MemberAccess expressions. This fixes #28412.
-
- 26 8月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 11 8月, 2017 1 次提交
-
-
由 Sam Harwell 提交于
-
- 02 8月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
* Rename Foo to Goo * Rename ifoo to igoo * Add back BOMs
-
- 07 7月, 2017 1 次提交
-
-
由 Sam Harwell 提交于
-
- 29 6月, 2017 1 次提交
-
-
由 Sam Harwell 提交于
-
- 28 2月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 09 12月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 21 7月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 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.
-
- 18 11月, 2015 1 次提交
-
-
由 Jonathon Marolf 提交于
-
- 11 11月, 2015 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 16 10月, 2015 1 次提交
-
-
由 Paul Harrington 提交于
-
- 10 10月, 2015 1 次提交
-
-
由 Tanner Gooding 提交于
-
- 07 7月, 2015 1 次提交
-
-
由 Charles Stoner 提交于
-
- 01 7月, 2015 1 次提交
-
-
由 Charles Stoner 提交于
-
- 10 6月, 2015 1 次提交
-
-
由 Charles Stoner 提交于
-
- 04 6月, 2015 2 次提交
-
-
由 Jonathon Marolf 提交于
Responding to peer review feedback. Updated to never consider user defined narrowing conversions unnecessary.
-
由 Jonathon Marolf 提交于
Fixes #3161 and Fixes #3163 User Scenario: User has code with narrowing conversion with an explicit cast. We will offer to remove the cast even though this will cause the code to not compile. Fix Description: We previously never consulted optionstrict to determine if a user-defined narrowing cast was necessary. The fix in CastAnalyzer.vb will check if the conversion is narrowing, if option strict is on, or if we generate a warning on implicit narrowing conversions. We also offer to add a cast if an implicit conversion warning is given. Testing: Added regression tests + existing tests
-
- 03 6月, 2015 1 次提交
-
-
由 Manish Vasani 提交于
Fix ITypeSymbolExtensions.IsOrDerivedFromExceptionType to handle type parameters constrained on Exception type or its subtype Fixes https://github.com/dotnet/roslyn/issues/3254 User scenario: User writes code where they have explicit casts to a type parameter deriving from Exception type or its subtype. We will offer incorrect cast removal fixes to remove these explicit casts. Removing such casts will cause their code to not compile. Even worse, if they apply a FixAll occurrences code fix, then all such casts across their (document/project/solution) will be removed, causing tons of compile errors. Fix description: IsOrDerivedFromExceptionType was only checking for base types of the given type symbol to detect if the type is an Exception type. We also need to handle type parameters which are constrained by Exception or its subtypes. Testing: Added regression tests + existing tests.
-
- 19 5月, 2015 1 次提交
-
-
由 Manish Vasani 提交于
For code snippets such as below: "Base M(Base b) => (Derived)b;", we currently offer cast removal for cast to derived. However, this involves an explicit/narrowing conversion and hence can lead to an exception or data loss. The only way to detect such redundant casts is via flow analysis, which is not currently in our scope. Fix is to bail out early for such cast expressions. I have also fixed incorrect tests that were added to ensure the current behavior. Fixes #2761
-
- 21 2月, 2015 1 次提交
-
-
由 Dustin Campbell 提交于
There are legitimate cases where removing a cast inside a string interpolation can case the open brace of the interpolation to touch the open brace on an array literal, resulting in a broken parse (i.e. `{{`). This changes the Remove Unnecesary Cast code fix to add parentheses outside of the cast rather than around the inner expression. Then, the parenthesis simplifier has been updated to correctly handle the case where an array literal touches the start of an interpolation: Dim x = $"{({})}" Fixes Issue #739.
-
- 29 1月, 2015 1 次提交
-
-
由 beep boop 提交于
-