- 01 11月, 2018 2 次提交
-
-
由 Neal Gafter 提交于
Fixes #30282
-
由 Neal Gafter 提交于
Fixes #29297 Also Skip tests broken by changes. See #30848
-
- 27 10月, 2018 2 次提交
-
-
由 Neal Gafter 提交于
Merge master into features/recursive-patterns
-
由 Neal Gafter 提交于
Fixes #30788 Relates to #30795 and #30794
-
- 26 10月, 2018 1 次提交
-
-
- 24 10月, 2018 4 次提交
-
-
由 Jared Parsons 提交于
Fix Linux log publish
-
由 Rikki Gibson 提交于
* Check for restricted return types on local functions * Add test for restricted local function returns * Add test for local function ref parameters of restricted types * Add test to demonstrate that local functions can return Span<T>
-
由 Pär Björklund 提交于
Only enabled for C#8 or above to avoid suggesting fixes that break compilation.
-
由 Šimon Koníček 提交于
Adding UseExplicitTypeForConstCodeFixProvider - Not offering the fix for multiple declarators - Not offering regular UseExplicitType code fix and refactoring for constants
-
- 23 10月, 2018 2 次提交
-
-
由 Jared Parsons 提交于
-
由 Neal Gafter 提交于
Fixes #30543
-
- 22 10月, 2018 1 次提交
-
-
由 Sam Harwell 提交于
Fixes issue #30529 "object initializers and csharp_new_line_before_open_brace in editorconfig"
-
- 21 10月, 2018 1 次提交
-
-
由 Thomas Rzipa 提交于
-
- 20 10月, 2018 19 次提交
-
-
由 Dustin Campbell 提交于
MSBuildWorkspace needs to set a property to ensure that project references are built with the correct configuration
-
由 dotnet-automerge-bot 提交于
Merge dev16.0.x to master
-
由 Dustin Campbell 提交于
-
由 Rainer Sigwald 提交于
-
由 Jason Malinowski 提交于
some code clean up on new VisualStudioProject and FileChangeWatcher
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
-
由 Dustin Campbell 提交于
Essentially, this change stops passing global properties around and makes the ProjectBuildManager own a set of global properties. This improves general sanity.
-
由 Dustin Campbell 提交于
-
由 dotnet-automerge-bot 提交于
Merge dev16.0.x to master
-
由 Rikki Gibson 提交于
* Handle collection initializers which lower to an extension method call with a `ref this` parameter * Simplify RefKind check * Add more tests for combinations of in params and implicit temporaries * Replace methodOrIndexer.Parameters usages with @params * Add asserts about parameter RefKinds and comments * Add tests for more combinations of ref and in parameters * Add WorkItem attributes to tests * Take master version of LocalRewriter_Call * Check that ImplicitReceiver valueKind is not RefAssignable * Fix conventions in diagnostics tests * Change RefAssignableVariable check to debug assert This assertion and return statement expresses that we expect the BoundImplicitReceiver to be lowered into a temporary local (not ref-assignable) if needed to satisfy the BindValueKind of the usage. This assertion ensures that if a new usage down the line requires the BoundImplicitReceiver to be ref-assignable, we reexamine our assumptions here and specify when the BoundImplicitReceiver can be ref-assignable. * Disable GenericBaseTypeHasNonVirtualFinalize on Mono
-
由 Dustin Campbell 提交于
-
由 Jared Parsons 提交于
Inject range indexers
-
由 HeeJae Chang 提交于
first is clean up on some lock usage that is no longer needed. second is fixing a bug where it doesn't support same web page to be opened again after closed.
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
-
由 Sam Harwell 提交于
Do not convert mutable value type fields to properties
-
由 CyrusNajmabadi 提交于
-
- 19 10月, 2018 8 次提交
-
-
由 Manish Vasani 提交于
Fix for perf issues in CompilationWithAnalyzers found from perf traces
-
由 Charles Stoner 提交于
-
由 Manish Vasani 提交于
-
由 Andy Gocke 提交于
-
由 Andy Gocke 提交于
Generates fake indexers for arrays that take System.Index and System.Range.
-
由 Jason Malinowski 提交于
This produces a new free-threaded, well factored API for adding projects to the VisualStudioWorkspace. The core type is the VisualStudioProject which is a free-threaded API that you can use to push information over. CSharpProjectShim, VisualBasicProject and CPSProject each have an instance of VisualStudioProject that they push things through. This also introduces a proper batching API: any consumer of VisualStudioProject may call CreateBatchScope() which means all future operations are put a single batch that will be applied at once in a single workspace change. Multiple calls to CreateBatchScope just stack: it only applies when all scopes are closed. You could think of the behavior as roughly analogous to an SQL transaction, except with no rollback capabilities. A batch is only per-project: a batch started on one project doesn't impact another project. There is no concept of a cross-project batch, short of just starting two independent batches and completing them at the same time (which creates two workspace changes.) The inheritance model here is now smaller. CSharpProjectShim and VisualBasicProject inherit from AbstractLegacyProject, but that's it. CPSProject now inherits nothing, and AbstractProject is here purely for TypeScript back-compat until they're moved onto the new APIs. The expectation is F# and TypeScript both move to VisualStudioProject, which we make public in some form. Then AbstractProject will go away. AbstractLegacyProject (which is used for csproj and vbproj) still is tied to the UI thread, but the ties should now be more limited and better understood. The primary tangles right now are having to fetch a few things from IVsHierarchies, namely some project properties and the folder structure. The plan for now is AbstractLegacyProject-derived projects will still be called on the UI thread, and we'll determine a new API to remove those remaining issues for them (or just move them onto VisualStudioProject.) The threading guarantee given to all consumers of VisualStudioProject is it can be called from any thread, and no synchronous calls to the UI thread may be done at that time. There are a few places where we asynchronously kick off work to inspect the running document table, but those are async and should never block. There is a lock hierarchy now instituted: each VisualStudioProject has a lock which it takes when any method is called on it, this is to ensure straightforward synchronization of it's data for things like batch start/stopping, what's in the batch, etc. There is also a lock in VisualStudioWorkspaceImpl that is acquired when actually modifying the workspace, which is done through an internal ApplyChangeToWorkspace method so it can be called from VisualStudioProject more easily. It is permissible for a VisualStudioProject to call ApplyChangeToWorkspace to acquire the VisualStudioWorkspaceImpl lock. It is _not_ permissible for a lock holder of VisualStudioWorkspaceImpl's lock to acquire any project lock. To this end, some project-to-project tracking information is held in VisualStudioWorkspaceImpl to avoid mistakes -- although the data is a "per project" concept, putting it in the project would cause people to take a project lock and risk deadlocks.
-
由 Charles Stoner 提交于
-
由 Heejae Chang 提交于
This adds an API for the project system to notify us about files that can generate .cs files in the workspace. The rest of the implementation is still coming but this unblocks the project system side of things.
-