- 31 3月, 2018 1 次提交
-
-
由 Sam Harwell 提交于
-
- 24 3月, 2018 2 次提交
-
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
Closes #25560
-
- 21 3月, 2018 1 次提交
-
-
由 Sam Harwell 提交于
-
- 03 3月, 2018 1 次提交
-
-
由 Heejae Chang 提交于
* updated matrix for unreachable code case * more unreachable tests * updated comments * add support for local function
-
- 18 1月, 2018 1 次提交
-
-
由 Oleg Tkachenko 提交于
-
- 23 8月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 02 8月, 2017 1 次提交
-
-
由 CyrusNajmabadi 提交于
* Rename Foo to Goo * Rename ifoo to igoo * Add back BOMs
-
- 29 6月, 2017 1 次提交
-
-
由 Sam Harwell 提交于
-
- 16 6月, 2017 1 次提交
-
-
由 Andy Gocke 提交于
By design, when data flow analyzes local functions it does so devoid of surrounding context and records possibly unassigned variables rather than reporting a diagnostic. Thus, all captured variables are expected to be marked unassigned during data flow analysis without reporting a diagnostic. However, reporting a diagnostic is not the only side effect of running data flow analysis. By calling virtual methods data flow analysis informs derived types of unassigned variables. While the diagnostic is suppressed and recorded, currently the virtual method is still called. This has negative consequences for region analysis, which considers these calls as indications of variables flowing out of the given region, which may not be the case for local functions. This PR changes data flow analysis to only call the ReportUnassigned virtual method if not inside a local function, excluding local functions from all unassignment reporting. Fixes #17165, #18347
-
- 02 6月, 2017 2 次提交
-
-
由 Sam Harwell 提交于
Closes #19136
-
由 Sam Harwell 提交于
Fixes #17474
-
- 01 3月, 2017 2 次提交
-
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
- 14 1月, 2017 1 次提交
-
-
由 Andy Gocke 提交于
Temporarily marks data flow analysis over a region which contains local functions as "failed." The current implementation is incorrect, so data flow analysis should mark the result as bad rather than knowingly give an incorrect result. This change also causes extract method to emit a warning when extracting over a region which involves local functions. Fixes #15532, #16116, #8719, #8718, #8717
-
- 03 11月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 26 1月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
-
- 16 1月, 2016 2 次提交
-
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
- 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.
-
- 20 11月, 2015 1 次提交
-
-
由 Cyrus Najmabadi 提交于
-
- 19 11月, 2015 2 次提交
-
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
- 04 11月, 2015 1 次提交
-
-
由 Neal Gafter 提交于
-
- 28 10月, 2015 1 次提交
-
-
由 Kevin Pilch-Bisson 提交于
-
- 16 10月, 2015 1 次提交
-
-
由 Paul Harrington 提交于
-
- 11 10月, 2015 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 10 10月, 2015 2 次提交
-
-
由 Kevin Pilch-Bisson 提交于
-
由 Tanner Gooding 提交于
-
- 05 9月, 2015 1 次提交
-
-
由 Andrew Casey 提交于
...until we have time to think about which are the most valuable and how they should interact with previous submissions.
-
- 07 7月, 2015 1 次提交
-
-
由 Charles Stoner 提交于
-
- 27 5月, 2015 1 次提交
-
-
由 Tanner Gooding 提交于
This reverts 99317ad0.
-
- 23 5月, 2015 1 次提交
-
-
由 Charles Stoner 提交于
-
- 03 5月, 2015 1 次提交
-
-
由 Balaji Krishnan 提交于
Adding unit tests for Introduce variable and Extract Method in Nested Collection Initializer cases. The bug no longer reproes. This change is test only.
-
- 29 1月, 2015 1 次提交
-
-
由 beep boop 提交于
-