-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge main
into features/RefReadonly
#68486
Merged
jjonescz
merged 503 commits into
dotnet:features/RefReadonly
from
jjonescz:RefReadonly-main
Jun 8, 2023
Merged
Merge main
into features/RefReadonly
#68486
jjonescz
merged 503 commits into
dotnet:features/RefReadonly
from
jjonescz:RefReadonly-main
Jun 8, 2023
Conversation
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
…ptionsChange Add RequiresNonDocumentChangesTag to ProjectOptionsChangeAction
…med-types and methods. (dotnet#68131) * Use a singleton for empty type-parameters for named types * move type parameters down * Optimize methods as well * Always create indirection * Move type * Apply suggestions from code review * speeling * nrt * Inline * Simplify * Change to abstract override
…-release/dev17.5-vs-deps Merge release/dev17.4 to release/dev17.5-vs-deps
* Record added node output states as new The `(EntryState.Modified, EntryState.Added) => IncrementalStepRunReason.Modified` state mapping was recently added in dotnet#61308, but doesn't look correct to me. Since this value is used as the output status, and the outputs are new, I believe the correct state should be `IncrementalStepRunReason.New` instead. * Update tests that were added since I originally implemented the change * Update documentation for IncrementalStepRunReason * Update VB tests also * Add note about breaking changes with IncrementalStepRunReason --------- Co-authored-by: Jan Jones <[email protected]>
* Add a test * Display standalone parameter names by default * Document breaking change * Update tests
Avoid rooting document instances in NavigateToSearchResult
Deprecate CompilationWithAnalyzers.IsDiagnosticAnalyzerSuppressed public API
Avoid waiting on the thread pool when there is no work to do
Use a proper tool bar in Document Outline
Fix detection of nested symbols in Document Outline
Our PRs already run tests on Unix which is a sufficient proxy for Mac runs. Can leave Mac as CI only and slim down our PR runs
Fix 'use local function' with implicitly typed lambdas
Move off of recursion when determining pp-directive information for a file.
Switch to new lower-overhead spell checking protocol
…ervice-cleanups-and-perf-improvements Ensure we only ask for a symbol's documentation comment once
jjonescz
added
the
New Feature - Ref Readonly Parameters
`ref readonly` parameters
label
Jun 8, 2023
dotnet-issue-labeler
bot
added
Area-Infrastructure
untriaged
Issues and PRs which have not yet been triaged by a lead
labels
Jun 8, 2023
@dotnet/roslyn-compiler @jcouv @AlekseyTs need a sign-off on a clean merge |
AlekseyTs
approved these changes
Jun 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area-Infrastructure
New Feature - Ref Readonly Parameters
`ref readonly` parameters
untriaged
Issues and PRs which have not yet been triaged by a lead
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No conflicts.