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.

Sign up for GitHub

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

Jump to bottom

Fix S3459 FP: Backing field with ref property #9383

Merged
merged 4 commits into from
Jun 4, 2024
Merged

Fix S3459 FP: Backing field with ref property #9383

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d1d9ac8
Fix RefExpressionSyntax handling
martin-strecker-sonarsource Jun 4, 2024
fbb3aad
Fix UT
martin-strecker-sonarsource Jun 4, 2024
c92e764
Reivew 1
martin-strecker-sonarsource Jun 4, 2024
6490502
Remove duplicate snippet
martin-strecker-sonarsource Jun 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion analyzers/src/SonarAnalyzer.CSharp/Rules/NotAssignedPrivateMember.cs
View file
Open in desktop
Tim-Pohlmann marked this conversation as resolved.
Show resolved Hide resolved
Original file line number Diff line number Diff line change
Expand Up @@ -184,7 +184,8 @@ private static ISet<ISymbol> GetAssignedMemberSymbols(IList<MemberUsage> memberU

if (PreOrPostfixOpSyntaxKinds.Contains(parentNode.Kind())
|| (parentNode is AssignmentExpressionSyntax assignment && assignment.Left == node)
|| (parentNode is ArgumentSyntax argument && (!argument.RefOrOutKeyword.IsKind(SyntaxKind.None) || TupleExpressionSyntaxWrapper.IsInstance(argument.Parent))))
|| (parentNode is ArgumentSyntax argument && (!argument.RefOrOutKeyword.IsKind(SyntaxKind.None) || TupleExpressionSyntaxWrapper.IsInstance(argument.Parent)))
|| RefExpressionSyntaxWrapper.IsInstance(parentNode))
Copy link
Contributor

@Tim-Pohlmann Tim-Pohlmann Jun 4, 2024 •
edited
Loading

Choose a reason for hiding this comment

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

This is too simple and introduces an FN (run with C# 9):

    private int _foo; // FN
    public int Foo => _foo;
    void Method()
    {
        _ = ref _foo;
    }

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is not a FN. If you get a reference to the field, you have write access to it and that write can happen anywhere. This is like calling SomeMethod(ref field) where you do not know what happens inside SomeMethod. We would need to do symbolic execution on the assigned variable to properly detect all scenarios.

Copy link
Contributor

Choose a reason for hiding this comment

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

But you have access to the method where the ref was used. I accept that this is out of the scope of this ticket, but at least add a reproducer to document the limitation.

{
assignedMembers.Add(memberSymbol);
assignedMembers.Add(memberSymbol.OriginalDefinition);
Expand Down
2 changes: 1 addition & 1 deletion analyzers/tests/SonarAnalyzer.Test/TestCases/NotAssignedPrivateMember.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -205,7 +205,7 @@ public void Print()
// Reproducer: https://github.com/SonarSource/sonar-dotnet/issues/9106
public class Repro_9106
{
private int _foo; // Noncompliant FP
private int _foo; // Compliant

public ref int Foo => ref _foo;
}
Loading