Skip to content

Conversation

@AlekseyTs
Copy link
Contributor

No description provided.

CyrusNajmabadi and others added 30 commits March 15, 2025 13:16
…ence-packages build 20250314.1 (dotnet#77623)

Microsoft.SourceBuild.Intermediate.source-build-reference-packages
 From Version 10.0.616304 -> To Version 10.0.616401

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
…314.2 (dotnet#77624)

Microsoft.SourceBuild.Intermediate.arcade , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.XliffTasks
 From Version 9.0.0-beta.25161.4 -> To Version 9.0.0-beta.25164.2

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
…77603)

Specifically, two static extension methods are allowed to have the same signature
(according to the current language rules) as long as all the following conditions are met:
- methods have different return type and/or different return ref-ness
- methods extending different types (ref-ness of the receiver parameter is not considered)
…7620)

* Corrections to how we pick up roslyn options settings

* Cleanup

* Set default for Implement with Copilot to be false

* update for copilot.general.editor.enableGenerateDocumentationComment
I detected changes in the main branch which have not been merged yet to
main-vs-deps. I'm a robot and am configured to help you automatically
keep main-vs-deps up to date, so I've opened this PR.

This PR merges commits made on main by the following committers:

* tmat
* maryamariyan
* dotnet-maestro[bot]

## Instructions for merging from UI

This PR will not be auto-merged. When pull request checks pass, complete
this PR by creating a merge commit, *not* a squash or rebase commit.

<img alt="merge button instructions"
src="https://i.imgur.com/GepcNJV.png" width="300" />

If this repo does not allow creating merge commits from the GitHub UI,
use command line instructions.

## Instructions for merging via command line

Run these commands to merge this pull request from the command line.

``` sh
git fetch
git checkout main
git pull --ff-only
git checkout main-vs-deps
git pull --ff-only
git merge --no-ff main

# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge
# Pushing the changes to the PR branch will re-trigger PR validation.
git push https://github.com/dotnet/roslyn HEAD:merge/main-to-main-vs-deps
```

<details>
<summary>or if you are using SSH</summary>

```
git push git@github.com:dotnet/roslyn HEAD:merge/main-to-main-vs-deps
```

</details>


After PR checks are complete push the branch
```
git push
```

## Instructions for resolving conflicts

:warning: If there are merge conflicts, you will need to resolve them
manually before merging. You can do this [using GitHub][resolve-github]
or using the [command line][resolve-cli].

[resolve-github]:
https://help.github.com/articles/resolving-a-merge-conflict-on-github/
[resolve-cli]:
https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/

## Instructions for updating this pull request

Contributors to this repo have permission update this pull request by
pushing to the branch 'merge/main-to-main-vs-deps'. This can be done to
resolve conflicts or make other changes to this pull request before it
is merged.
The provided examples assume that the remote is named 'origin'. If you
have a different remote name, please replace 'origin' with the name of
your remote.

```
git fetch
git checkout -b merge/main-to-main-vs-deps origin/main-vs-deps
git pull https://github.com/dotnet/roslyn merge/main-to-main-vs-deps
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet/roslyn HEAD:merge/main-to-main-vs-deps
```

<details>
    <summary>or if you are using SSH</summary>

```
git fetch
git checkout -b merge/main-to-main-vs-deps origin/main-vs-deps
git pull git@github.com:dotnet/roslyn merge/main-to-main-vs-deps
(make changes)
git commit -m "Updated PR with my changes"
git push git@github.com:dotnet/roslyn HEAD:merge/main-to-main-vs-deps
```

</details>

Contact .NET Core Engineering (dotnet/dnceng) if you have questions or
issues.
Also, if this PR was generated incorrectly, help us fix it. See
https://github.com/dotnet/arcade/blob/main/.github/workflows/scripts/inter-branch-merge.ps1.
Updates program to generate new description map when analyzers are added.
AlekseyTs and others added 9 commits March 26, 2025 09:52
- BoundCollectionElementInitializer.InvokedAsExtensionMethod
- BoundCall.InvokedAsExtensionMethod
- BoundDelegateCreationExpression.IsExtensionMethod
- MethodGroup.IsExtensionMethodGroup
- MethodGroupResolution.IsExtensionMethodGroup
…ntedExceptionDiagnosticAnalyzer.cs

Co-authored-by: Cyrus Najmabadi <cyrus.najmabadi@gmail.com>
Every time a developer uses the 💡 `Generate Method` feature in VS,
then with a ctrl+dot the cursor gets placed on the name of the newly
generated method which by default contains `throw new
NotImplementedException()`:


https://github.com/user-attachments/assets/5aa69115-6660-43c4-b711-eaa0f4772d8d

To help the discoverability and usability of `Implement with Copilot`,
especially for the developers frequently using the `Generate Method`
feature, I am making the analyzer diagnostic for `Implement with
Copilot` also light up on the method or property name containing the
`NotImplementedException` throw nodes.
@AlekseyTs AlekseyTs requested review from 333fred and cston March 27, 2025 03:25
@AlekseyTs AlekseyTs requested review from a team as code owners March 27, 2025 03:25
@dotnet-policy-service dotnet-policy-service bot added VSCode Needs UX Triage Needs API Review Needs to be reviewed by the API review council labels Mar 27, 2025
@dotnet-policy-service
Copy link
Contributor

This PR modifies public API files. Please follow the instructions at https://github.com/dotnet/roslyn/blob/main/docs/contributing/API%20Review%20Process.md for ensuring all public APIs are reviewed before merging.

@ghost ghost added the untriaged Issues and PRs which have not yet been triaged by a lead label Mar 27, 2025
@AlekseyTs
Copy link
Contributor Author

@cston, @333fred, @dotnet/roslyn-compiler Need a sign-off on a merge PR

@AlekseyTs AlekseyTs enabled auto-merge March 27, 2025 03:29
@AlekseyTs AlekseyTs merged commit 2c74f00 into dotnet:features/UserDefinedCompoundAssignment Mar 27, 2025
27 of 29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Compilers Needs API Review Needs to be reviewed by the API review council Needs UX Triage untriaged Issues and PRs which have not yet been triaged by a lead VSCode

Projects

None yet

Development

Successfully merging this pull request may close these issues.