On Sat, Mar 1, 2014 at 3:26 AM, Zack Weinberg <za...@panix.com> wrote: > > Then, when you get a false-positive maybe-uninitialized warning, you > could just replace T var; with mfbt::ConditionalUse<T> var; In a > release build, there would be no overhead; in a debug or valgrind > build you would get a prompt assertion on an invalid use. For > particularly dangerous-to-use-uninitialized types (e.g. pointers) the > release build could specialize the template to initialize the value to > a poison pattern. > > Thoughts?
Interesting! But won't you still get warnings in opt builds? Nick _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
