- 05 8月, 2016 1 次提交
-
-
由 Tomáš Matoušek 提交于
* Implement source link feature * Fix CommonCompiler to open source link stream, add E2E tests * Reduce code duplication across VB and C#
-
- 21 7月, 2016 2 次提交
-
-
由 Julien 提交于
- 20 7月, 2016 2 次提交
-
-
由 Charles Stoner 提交于
[Based on features/async-return with tests ported from that branch.]
-
由 CyrusNajmabadi 提交于
-
- 15 7月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 13 7月, 2016 1 次提交
-
-
由 Andy Gocke 提交于
For the most part, this change implements the same encoding for tuples that we use for dynamic. This means that interface implementations and generic constraints are not covered, but base types and type parameters are. This change also doesn't have full tests for "long" tuples (nested tuple transformations) or tuple types that can only be constructed in metadata.
-
- 11 7月, 2016 1 次提交
-
-
由 VSadov 提交于
-
- 24 6月, 2016 1 次提交
-
-
由 gafter 提交于
-
- 01 6月, 2016 1 次提交
-
-
由 Charles Stoner 提交于
-
- 21 5月, 2016 2 次提交
- 04 5月, 2016 1 次提交
-
-
由 AlekseyTs 提交于
- Substitute underlying type with corresponding tuple type at the point of type reference. - Adjusted implementation of symbol display to account for presence of names in the extension tuples. - Implemented proper retargeting for tuple types (multi-targeting support).
-
- 01 5月, 2016 1 次提交
-
-
由 AlekseyTs 提交于
- Include memebers of underlying type into a set of members returned by tuple type symbol. Properties and events are not supported at the moment. - Track declaration locations for tuple related symbols. - Ensure Rest extensions are tuples.
-
- 28 4月, 2016 1 次提交
-
-
由 Julien 提交于
-
- 22 4月, 2016 1 次提交
-
-
由 Manish Vasani 提交于
-
- 21 4月, 2016 2 次提交
-
-
由 Manish Vasani 提交于
Ensure that we generated a CompilationCompletedEvent for compilations with no source files (example an empty VSIX projects).
-
由 Manish Vasani 提交于
Ensure that we generated a CompilationCompletedEvent for compilations with no source files (example an empty VSIX projects).
-
- 20 4月, 2016 1 次提交
-
- 16 4月, 2016 1 次提交
-
- 07 4月, 2016 1 次提交
-
-
由 Charles Stoner 提交于
-
- 02 4月, 2016 1 次提交
-
-
由 Charles Stoner 提交于
-
- 30 3月, 2016 1 次提交
-
-
由 Charles Stoner 提交于
-
- 29 3月, 2016 1 次提交
-
-
由 Charles Stoner 提交于
-
- 18 3月, 2016 1 次提交
-
-
由 Julien Couvreur 提交于
-
- 17 3月, 2016 2 次提交
-
-
由 Neal Gafter 提交于
Fixes #9759
-
由 Neal Gafter 提交于
Fixes #9759
-
- 09 3月, 2016 2 次提交
-
- 04 3月, 2016 1 次提交
-
-
由 Tomas Matousek 提交于
-
- 03 3月, 2016 1 次提交
-
-
由 Gen Lu 提交于
The flag name is "IOperation". Register opeartion actions and calling SemanticModel.GetOperation while the feature is disabled will throw an InvalidOperationException. Also log a non-fatal-watson when SemanticModel.GetOperation crashes.
-
- 24 2月, 2016 1 次提交
-
-
由 Neal Gafter 提交于
Fixes #7477
-
- 20 2月, 2016 1 次提交
-
-
由 Neal Gafter 提交于
-
- 19 2月, 2016 1 次提交
-
-
由 Neal Gafter 提交于
and use that to diagnose cases where the compiler produces compilation events later than it should.
-
- 18 2月, 2016 2 次提交
-
-
由 Andrew Casey 提交于
Scripting scenarios set a special flag in the ReferenceManager to enable additional tie-breaking rules in the presence of conflicting references. Enable that same flag for the EE, which also routinely encounters conflicting references. Fixes internal bug 161294.
-
由 Neal Gafter 提交于
Fixes #8178
-
- 10 2月, 2016 1 次提交
-
-
由 CyrusNajmabadi 提交于
-
- 26 1月, 2016 1 次提交
-
-
由 Brett V. Forsgren 提交于
-
- 18 12月, 2015 1 次提交
-
-
由 Manish Vasani 提交于
1. Add a new API: AnalysisContext.ConfigureGeneratedCodeAnalysis(GeneratedCodeAnalysisFlags analysisMode) Configures analyzer callbacks + diagnostic reporting for the analyzer. Recommended for analyzer authors to always invoke this API. 2. Analyzer driver uses a heuristic to identify generated code: 1. Symbols marked with GeneratedCodeAttribute. 2. Files with specific extensions (see [here](http://source.roslyn.io/Microsoft.CodeAnalysis.Workspaces/R/ef3599fb042e3706.html)). 3. Files which have a single line comment starting with <auto-generated> at the beginning of a source file. 3. Driver defaults for non-configured analyzers: 1. Run analysis on generated code: This avoids semantic breaks for analyzers and will be guaranteed to be always enabled in future. 2. Report all diagnostics on generated code: This will likely be changed to perform some level of default filtering after #3705 is implemented. Fixes #6998
-
- 04 11月, 2015 1 次提交
-
-
由 Neal Gafter 提交于
-