Bug 12488 - Incorrect "variable could be move to nested scope" suggestion
Summary: Incorrect "variable could be move to nested scope" suggestion
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: master
Assignee: Mike Krüger
Depends on:
Reported: 2013-05-31 11:08 UTC by Mikayla Hutchinson [MSFT]
Modified: 2013-06-07 01:34 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 Mikayla Hutchinson [MSFT] 2013-05-31 11:08:15 UTC
Source analysis here suggests that the variable could be moved to a nested scope. Although that would compile, it's incorrect, as it would change the logic of the code: http://screencast.com/t/c58A2ejP

IMO source analysis should not make this suggestion unless
* the variable is assigned a constant expression
* it would not move "past" method/property invocations or field assignments
Comment 1 Mike Krüger 2013-06-07 01:34:55 UTC