Skip to content

Conversation

@dotnet-bot
Copy link
Collaborator

This is an automatically generated pull request from release/dev16.7 into release/dev16.7-vs-deps.

git fetch --all
git checkout merges/release/dev16.7-to-release/dev16.7-vs-deps
git reset --hard upstream/release/dev16.7-vs-deps
git merge upstream/release/dev16.7
# Fix merge conflicts
git commit
git push upstream merges/release/dev16.7-to-release/dev16.7-vs-deps --force

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

allisonchou and others added 13 commits June 25, 2020 12:28
…) in records with the latest design. (#45475)

* Align addition of a synthesized override of object.Equals(object? obj) in records with the latest design.

Related to #45296.

From specification:
The record type includes a synthesized override of object.Equals(object? obj). It is an error if the override is declared explicitly. The synthesized override returns Equals(other as R) where R is the record type.
…eferences

If you have two projects that reference each other with metadata
references, we should avoid converting both of them into project
references as that causes a circularity in the Workspace layer.
The workspace API correctly throws exceptions if you try to do this,
but the Visual Studio project system layer wasn't checking, and so it'd
call into the Workspace APIs and throw exceptions. Unfortunately this
often resulted in us getting into corrupted states where the data
structures got out of sync, which might later result in other exceptions
too.

This fix isn't entirely correct in that we're not going to re-convert
the metadata reference to the project reference if something else breaks
the circularity; that's better than crashing so this is an improvement
either way.

Fixes #39904
Fixes #43633
Co-authored-by: AlekseyTs <AlekseyTs@users.noreply.github.com>
Prevent trying to convert metadata references into circular project references
This reverts commit f755e8a. That
change meant our EditorFeatures code was using DllImports in the
cross-platform binary, and we weren't sure what that would do in
VS for Mac if that code ran. It also brought a dependency on
Microsoft.VisualStudio.RemoteControl, which also seems to depend on
various Windows specific APIs.

We'll finish up the decision of what to do in
#45115
Inline rename highlight color in Dark Theme only has a contrast ratio of 1.238:1, and the target is 1.5:1

Original Color: #A6F1A6
New Color: #D3F8D3

Contrast ratio is 1.485:1 with new color

Resolves: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1139737
…earch-to-editorfeatures

Revert "Move SymbolSearch down to EditorFeatures (#45505)"
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

sharwell and others added 7 commits June 29, 2020 17:06
Change Signature: Fix for NullReferenceException when trying to add parameter with type modifier
Allow independent methods to have the same parameter name
[LSP] Remove snippets from completion list until they are supported
@sharwell sharwell merged commit c911f56 into release/dev16.7-vs-deps Jul 1, 2020
@sharwell sharwell deleted the merges/release/dev16.7-to-release/dev16.7-vs-deps branch July 1, 2020 06:27
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.

9 participants