- 19 5月, 2015 6 次提交
-
-
由 Heejae Chang 提交于
-
由 Heejae Chang 提交于
-
由 David Poeschl 提交于
Allow snippets in Inline Diff View
-
由 David Poeschl 提交于
No conflicts on same-named locals of delegate types
-
由 Jason Malinowski 提交于
Use pkgdef matching the language
-
由 Paul Harrington 提交于
Allocation reductions in formatting.
-
- 18 5月, 2015 7 次提交
-
-
由 Jared Parsons 提交于
The following line inside GetAliasTarget was causing a deadlock in the compiler: bool won = ImmutableInterlocked.InterlockedInitialize(ref _aliasTargetDiagnostics, newDiagnostics.ToReadOnlyAndFree()); The ToReadOnlyAndFree call caused any lazy diagnostics present in the DiagnosticsBag to be promptly evaluated. As a part of evaluation the diagnostics could call back into other compiler code including AliasSymbol.GetAliasTarget. If that happened on the same AliasSymbol instance the compiler would enter a deadlock as _aliasTarget had already been set to a non-null value. The CompareExchange of _aliasTarget is effectively a lock statement ToReadOnlyAndFree is calling out to untrusted code. The fix is to stop doing this by just saving the DiagnosticBag directly vs. calling ToReadOnlyAndFree. This resolves DevDiv 1161400
-
由 Manish Vasani 提交于
Add a new command line compiler switch "/reportanalyzer" to report analyzer execution times
-
由 David Poeschl 提交于
Fixes internal TFS bug #831378 Invoke snippets on the DataBuffer instead of the EditBuffer. Once IVsExpansion.InsertExpansion/InsertNamedExpansion has been invoked on the correct buffer, all remaining processing is the same (formatting, end span tracking, and snippet functions all map their given spans down to the subject buffer for processing).
-
由 Paul Harrington 提交于
-
由 Kevin Pilch-Bisson 提交于
fixed typos mentioned in #2786 and #2787
-
由 David Poeschl 提交于
Fixes #1729 The C# implementation of IRenameRewriterLanguageService.LocalVariableConflict was returning conflicts any time a related invocation expression bound to a local/parameter, but this condition is not indicative of a conflict when the local/parameter is of a delegate type. This change prevents reporting this particular kind of conflict on references to locals & parameters of a delegate type.
-
由 Charles Stoner 提交于
EE: Ignore duplicate types from cor library Ignore types from the cor library that also exist in the other framework assemblies. This issue arises in the EE when compiling expressions against the runtime assemblies loaded in the debuggee for CoreCLR.
-
- 17 5月, 2015 2 次提交
-
-
由 Charles Stoner 提交于
-
由 Manish Vasani 提交于
Expose a public API for consumers of CompilationWithAnalyzers to clear off analyzer state cached during analyzer execution. Executing analyzers requires us to internally store state such as supported diagnostics, registered actions, exception handlers for analyzer exceptions, etc. for the entire lifetime of analyzers. However, the lifetime of the analyzer instances is controlled only by the analyzer host, i.e. the consumer of CompilationWithAnalyzers. We cannot implicitly clear this internal state when disposing CompilationWithAnalyzers as the analyzer host might be re-using the same analyzer instances across multiple CompilationWithAnalyzers instances. Fix is to expose an API on CompilationWithAnalyzers to allow the analyzer host to explicitly clear stored analyzer state, when it is done using analyzer instances. Long term solution is to make the AnalyzerManager public and remove its static instance, so that the analyzer host can explicitly control its lifetime. Fixes #2576
-
- 16 5月, 2015 25 次提交
-
-
由 Tomáš Matoušek 提交于
Adds an assert to clarify assumptions of GetAssemblyReferenceAlias
-
由 Tomáš Matoušek 提交于
Rollback fix d23b86, which turned out to break the EEs
-
由 Manish Vasani 提交于
Expose a public API for consumers of CompilationWithAnalyzers to clear off analyzer state cached during analyzer execution. Executing analyzers requires us to internally store state such as supported diagnostics, registered actions, exception handlers for analyzer exceptions, etc. for the entire lifetime of analyzers. However, the lifetime of the analyzer instances is controlled only by the analyzer host, i.e. the consumer of CompilationWithAnalyzers. We cannot implicitly clear this internal state when disposing CompilationWithAnalyzers as the analyzer host might be re-using the same analyzer instances across multiple CompilationWithAnalyzers instances. Fix is to expose an API on CompilationWithAnalyzers to allow the analyzer host to explicitly clear stored analyzer state, when it is done using analyzer instances. Long term solution is to make the AnalyzerManager public and remove its static instance, so that the analyzer host can explicitly control its lifetime.
-
由 Manish Vasani 提交于
Add a new command line compiler switch "/reportanalyzer" to report analyzer execution times. Output is grouped by analyzer assemblies and is displayed in descending order of execution times. NOTE: We do not display the total build time or the ratios between build time and analyzer execution time as the the actual wall clock time for analyzer execution is likely lesser due to multithreaded analyzer execution.
-
由 Kevin Halverson 提交于
Fix issue with locating source method in optimized code...
-
由 Kevin Halverson 提交于
We were previously assuming that "this" was always hoisted in async/iterator state machines. This is not true in optimized code. (fixes #2406)
-
由 Paul Harrington 提交于
-
由 noopbug 提交于
-
由 Shyam N 提交于
Fix expander to not crash when it encounters alias that binds to a missing namespace.
-
由 Tomáš Matoušek 提交于
Fix issue where stdout and input aren't interleaving correctly
-
由 Heejae Chang 提交于
-
由 Andrew Casey 提交于
Expand transparent identifier in the (VB) EE
-
由 Heejae Chang 提交于
-
由 Tomas Matousek 提交于
-
由 Roman Pavlov 提交于
-
由 dino 提交于
-
由 Dustin Campbell 提交于
Rationalize Code Model "member node" logic
-
由 Shyam N 提交于
Fixes #1913 When expander encounters an alias identifier that binds to a unbound namespace, it would fall through a code path that would throw NotImplementedException. This change fixes the expander to 'handle' this case without crashing (by simply retruning the IdentifierNameSyntax for the namespace that the alias binds to). I discovered a difference in behavior between VB and C# SemanticModel which means that although I added a corresponding change to VB's expander, my fix is never invoked. I have logged #2805 for the difference and added a skipped test.
-
由 Tomas Matousek 提交于
-
由 Heejae Chang 提交于
-
由 Tanner Gooding 提交于
Revert change to VS Setup to include the build task
-
由 Tanner Gooding 提交于
-
-
由 dino 提交于
Add ability to write to std err and get the resulting span
-
由 Andrew Casey 提交于
...the same way we expand display classes and state machines. If we see a local or parameter with a transparent identifier generated/mangled name, we should instead include the properties of its (anonymous) type in our list of bindable symbols. This is a port of ec4d462d There is one notable difference between C# and VB: whereas C# has a single mangled name for transparent identifiers, VB has four - $VB$It, $VB$It1, $VB$It2, and $VB$ItAnonymous. Fortunately, the differences are not interesting to the EE - they're only to prevent name collisions (except $VB$ItAnonymous which is used when the value is not an anonymous type and does not need to be expanded).
-