From 218558e0840ce6a92bbc2edf290435acdcbd36a9 Mon Sep 17 00:00:00 2001 From: Maksym Koshovyi Date: Thu, 5 Sep 2019 02:11:56 +0300 Subject: [PATCH] Update Title according to suggestion Co-Authored-By: Genevieve Warren --- .../MicrosoftQualityGuidelinesAnalyzersResources.resx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/Microsoft.CodeQuality.Analyzers/Core/QualityGuidelines/MicrosoftQualityGuidelinesAnalyzersResources.resx b/src/Microsoft.CodeQuality.Analyzers/Core/QualityGuidelines/MicrosoftQualityGuidelinesAnalyzersResources.resx index c78f7e3a65..f3139b2fa6 100644 --- a/src/Microsoft.CodeQuality.Analyzers/Core/QualityGuidelines/MicrosoftQualityGuidelinesAnalyzersResources.resx +++ b/src/Microsoft.CodeQuality.Analyzers/Core/QualityGuidelines/MicrosoftQualityGuidelinesAnalyzersResources.resx @@ -256,9 +256,9 @@ Object '{0}' is referenced and reassigned in the same statement. You are at risk of referring to unintended object. - Referring to object and reassigning it in the same statement. + Referencing object and reassigning it in the same statement. When you go through the assignment chain right to left, firstly, reference in object '{0}' will be changed, but when you reffer to this object second time, since it's still the same statement, it will be pointing to it's old value. So if old value of '{0}' isn't saved elsewhere, result of the latter assignment will be lost. - \ No newline at end of file +