The developer must now solve the puzzle of why this re-assignment (on line (c)) is not preventing the warning all the way down on line (f).But not before noticing the write to my_string on line (c). Eventually, once satisfied that the move on line (e) is actually unreachable (oops!), the developer recommences the upwards traversal, eventually landing on the move on line (a).To realize that this is a red-herring requires evaluating the condition on line (d), which requires tracing even higher up into the function’s depths, delving further into the confusing business logic. Starting at the warning location and looking a few lines up, the take_ownership(std::move(my_string)) on line (e) immediately offers itself up as the culprit.(f)Īs in the simple example, a developer tasked with solving this bug will be looking to answer the question: where is my_string moved? A natural approach would likely be to start on line (f), and to scan backwards through the code. Use_string(my_string) // Use of a moved from object: ''my_string'' (lifetime.1). Take_ownership(std::move(my_string)) // (e) If (my_flag & !some_other_condition) // (d) Take_ownership(std::move(my_string)) // (a) Std::string new_string_owner = std::move(string_owner) Std::string string_owner = 'this string will be moved!' Warning C26800 catches code that attempts to use an object that is in a moved-from state: #include This blog post highlights how Key Events may be used with warning C26800 Use of a moved from object to quickly narrow down the problematic code. MSVC’s Code Analysis Key Events are a useful tool for quickly getting to the root-cause of your static analysis warnings.

Xamarin visual studio 2008