Bug 10733 - Auto-Fix regarding control flow: "Unused variable assignment can be removed"
Summary: Auto-Fix regarding control flow: "Unused variable assignment can be removed"
Status: RESOLVED DUPLICATE of bug 11579
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: 4.0
Hardware: PC Linux
: Normal enhancement
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2013-02-27 08:41 UTC by Ciprian Khlud
Modified: 2013-04-04 10:39 UTC (History)
1 user (show)

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:

Description Ciprian Khlud 2013-02-27 08:41:22 UTC
Reference to bug #10717 comment 1
Add an Auto-Fix that simplify blocks of code:

Steps to reproduce:
Write a code that matches this pattern:

$var = FunctionCall();
//later var is not "read" later

Expected result:
Should be an Auto-Fix solution that simplify the expression by rewriting it in this form:

Note: $var should be a local declared variable.
Comment 1 Ciprian Khlud 2013-02-27 09:24:35 UTC
There is a case of the same Auto-fix:
var $var_name = FunctionCall();
and this var_name is not used subsequently.
Comment 2 Mike Krüger 2013-04-04 10:39:13 UTC
Should be fixed by #11579

*** This bug has been marked as a duplicate of bug 11579 ***