Skip to content

Conversation

ScottCarda-MS
Copy link
Contributor

@ScottCarda-MS ScottCarda-MS commented Dec 12, 2024

Makes the set keyword optional for assignment expressions. Adds a lint and code action to deprecate the use of the set keyword. The lint level is set to "Allow".

Closes #1496

Copy link
Collaborator

@swernli swernli left a comment

Choose a reason for hiding this comment

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

A couple minor comments on the lint portion, but otherwise quite happy with how this turned out!

@sezna sezna mentioned this pull request Dec 14, 2024
9 tasks
Copy link
Collaborator

@swernli swernli left a comment

Choose a reason for hiding this comment

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

Looked at the new lint, phrasing is consistent and should be helpful to folks!

@ScottCarda-MS ScottCarda-MS added this pull request to the merge queue Dec 16, 2024
Merged via the queue into main with commit 8fefdd5 Dec 16, 2024
18 checks passed
@ScottCarda-MS ScottCarda-MS deleted the sccarda/RemoveSet branch December 16, 2024 22:18
github-merge-queue bot pushed a commit that referenced this pull request Mar 18, 2025
The language samples still stated:

> // Mutable variables can be mutated with the `set` keyword

Technically this is true, but since `set` is now
[deprecated](#2062) I removed it
from all the samples.

---------

Co-authored-by: Mine Starks <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make set keyword optional and include lint to suggest avoiding it.
3 participants