Bug 10753 - Const value incorrectly marked redundant
Summary: Const value incorrectly marked redundant
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: PC Windows
: Low normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2013-02-28 01:34 UTC by Mikayla Hutchinson [MSFT]
Modified: 2013-02-28 07:37 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-02-28 01:34:52 UTC
From: http://forums.xamarin.com/discussion/1725/xamarin-studio-source-analysis-const-issue#latest

Using this line:

const int MinValue = 0;

Source Analysis suggests to remove the redundant field initializer. However, if I remove the initialization the compiler produces an error as a const variable needs to be initialized. I guess Source Analysis isn't properly fine tuned here.
Comment 1 Mike Krüger 2013-02-28 07:37:14 UTC