[c#] initial support for replacing setter assignments with setter calls #5290
Conversation
This file contains hidden or 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
|
|
||
| protected def astForBinaryExpression(binaryExpr: DotNetNodeInfo): Seq[Ast] = { | ||
| private def translateBinaryOperatorName(operatorToken: String): Option[String] = { | ||
| Map( |
There was a problem hiding this comment.
This map could be statically defined once in the companion object.
DavidBakerEffendi
approved these changes
Feb 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Renders setter assignments as their corresponding
set_PropertyNamecalls, e.g.x.MyProperty = yroughly becomesx.set_MyProperty(y). There are still some edges to be addressed in future PRs; in particular, we should have a general solution for building signatures so we don't keep falling for them.