Bug 14685 - mcs doesn't properly detect use of uninitialized locals
Summary: mcs doesn't properly detect use of uninitialized locals
Alias: None
Product: Compilers
Classification: Mono
Component: C# ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Marek Safar
Depends on:
Reported: 2013-09-12 12:38 UTC by Jeffrey Stedfast
Modified: 2013-11-27 10:10 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 GitHub or Developer Community 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 Jeffrey Stedfast 2013-09-12 12:38:43 UTC
using System;

namespace CompilerBug
    class Program
        public static void Main(string[] args)
            int number;
            string text = args[0] != null ? GetSomeStuff(out number) : string.Empty;

            Console.WriteLine("compiling this code should produce an error \"Use of unassigned local variable 'number'\": {0}, text = {1}", number, text);

        static string GetSomeStuff(out int number)
            number = 5;
            return "5";
Comment 1 Jeffrey Stedfast 2013-09-12 12:43:44 UTC
I should mention that this is with
Comment 2 Marek Safar 2013-11-27 10:10:12 UTC
Fixed in master