forked from dotnet/roslyn
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'upstream/main' into ioperation-childope…
…rations * upstream/main: (875 commits) Merge pull request dotnet#54453 from davidwengier/FixBuild Move string to resources Fix window missing title. Move string to resources Fix test Update dependencies from https://github.com/dotnet/roslyn build 20210627.4 (dotnet#54441) Set AutoComplete based on CreateDraftPR Docs remove semantic version check Move to a simpler event source system for nav bars. Insertion depends on DARC publishing (dotnet#54420) Simplify delay Simplify delay Fix add parameter for records Insertion depends on DARC publishing (dotnet#54420) Fix move type for top level statements [main] Update dependencies from dotnet/source-build (dotnet#54384) Update DefaultDiagnosticModeServiceFactory.cs Create default option for lsp pull diagnostics to allow it to be switched on via feature flag Switch to correct workspace api to get active context Clean code ...
- Loading branch information
Showing
1,643 changed files
with
110,906 additions
and
22,727 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
# Dotnet-format -w Roslyn.sln | ||
abce41d282ac631be5217140f1bd46d0e250ad02 |
Validating CODEOWNERS rules …
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
--- | ||
name: API proposal | ||
about: Propose a change to the public API surface | ||
title: '' | ||
labels: [Feature Request, Concept-API] | ||
assignees: '' | ||
|
||
--- | ||
|
||
## Background and Motivation | ||
|
||
<!-- | ||
We welcome API proposals! We have a process to evaluate the value and shape of new APIs. There is an overview of our process [here](https://github.com/dotnet/roslyn/blob/main/docs/contributing/API%20Review%20Process.md). This template will help us gather the information we need to start the review process. | ||
First, please describe the purpose and value of the new API here. | ||
--> | ||
|
||
## Proposed API | ||
|
||
<!-- | ||
Please provide a sketch of the public API signature diff that you are proposing. Be as specific as you can: the more specific the proposal, the easier the process will be. An example diff is below. | ||
You may find the [Framework Design Guidelines](https://github.com/dotnet/runtime/blob/main/docs/coding-guidelines/framework-design-guidelines-digest.md) helpful. | ||
https://github.com/dotnet/roslyn/issues/53410 is a good example issue. | ||
--> | ||
|
||
```diff | ||
namespace Microsoft.CodeAnalysis.Operations | ||
{ | ||
public class ISwitchExpressionOperation | ||
{ | ||
+ public bool IsExhaustive { get; } | ||
} | ||
``` | ||
|
||
## Usage Examples | ||
|
||
<!-- | ||
Please provide code examples that highlight how the proposed API additions are meant to be consumed. | ||
This will help suggest whether the API has the right shape to be functional, performant and useable. | ||
You can use code blocks like this: | ||
``` C# | ||
// some lines of code here | ||
``` | ||
--> | ||
|
||
## Alternative Designs | ||
|
||
<!-- | ||
Were there other options you considered, such as alternative API shapes? | ||
How does this compare to analogous APIs in other ecosystems and libraries? | ||
--> | ||
|
||
## Risks | ||
|
||
<!-- | ||
Please mention any risks that to your knowledge the API proposal might entail, such as breaking changes, performance regressions, etc. | ||
--> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.