Bug 6742 - Incorrect "Redundant assignment" warning for local used in finally clause
Summary: Incorrect "Redundant assignment" warning for local used in finally clause
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2012-08-29 13:40 UTC by Mikayla Hutchinson [MSFT]
Modified: 2012-08-30 04:11 UTC (History)
1 user (show)

Tags: source-analysis
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Mikayla Hutchinson [MSFT] 2012-08-29 13:40:27 UTC
The "Redundant assignment" inspection incorrectly warns that there's a redundant assignment, even though the value is later accessed in the finally clause.

var a = new List<int> ();
try {
	Console.WriteLine (a.Count);
	a = null;
} finally {
	if (a != null) {
		Console.WriteLine ("error");
	}
}
Comment 1 Mike Krüger 2012-08-30 04:11:23 UTC
fixed that one.