Skip to content
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 to features/value_tracking #52553

Merged
90 commits merged into from
Apr 11, 2021

Conversation

dotnet-bot
Copy link
Collaborator

This is an automatically generated pull request from main into features/value_tracking.

Once all conflicts are resolved and all the tests pass, you are free to merge the pull request. 🐯

Troubleshooting conflicts

Identify authors of changes which introduced merge conflicts

Scroll to the bottom, then for each file containing conflicts copy its path into the following searches:

Usually the most recent change to a file between the two branches is considered to have introduced the conflicts, but sometimes it will be necessary to look for the conflicting lines and check the blame in each branch. Generally the author whose change introduced the conflicts should pull down this PR, fix the conflicts locally, then push up a commit resolving the conflicts.

Resolve merge conflicts using your local repo

Sometimes merge conflicts may be present on GitHub but merging locally will work without conflicts. This is due to differences between the merge algorithm used in local git versus the one used by GitHub.

git fetch --all
git checkout merges/main-to-features/value_tracking
git reset --hard upstream/features/value_tracking
git merge upstream/main
# Fix merge conflicts
git commit
git push upstream merges/main-to-features/value_tracking --force

Youssef1313 and others added 30 commits September 29, 2020 00:10
Co-authored-by: Joey Robichaud <joseph.robichaud@microsoft.com>
* Rebuild support for OutputKind

The `OutputKind` value was not properly round tripping through the PDB. Instead
we were only distinguishing between roughly exe and dll outputs. The compiler
though knows about six different output kinds and that both impacts the manner
in which compilation takes place as well as what values are encoded into the
PDB (impacts the `Subsystem` value for example). Properly round tripping the
output kind here.

* Fix

* PR feedback
Remove reliance on unreliable UpdateFile operation
Reset the interactive window using IInteractiveWindowOperations
Co-authored-by: Jason Malinowski <jason.malinowski@microsoft.com>
jmarolf and others added 21 commits April 8, 2021 14:34
"Add null check" inserts single line statements if preferred
Add publish data for d17p1 branch
Use CancellationSeries in ExternalErrorDiagnosticUpdateSource
Load NuGet assemblies on a background thread
* Remove use of Editor.INavigationBarItemService in LSP

Currently, the DocumentSymbolsHandler uses the editor version of INavigationBarItemService. Thanks to Cyrus's recent work around refactoring the nav bars for OOP, we now have a clean Features-layer API that we can seemlessly transition the handler to with minimal changes. I've done this, as well as a bit of general cleanup (enable nullable, fix a memory leak, a couple other things).
[main] Update dependencies from dotnet/roslyn
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approval

@ghost ghost merged commit 60224a1 into features/value_tracking Apr 11, 2021
@ghost ghost deleted the merges/main-to-features/value_tracking branch April 11, 2021 01:24
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.