<html><head><style data-externalstyle="true"><!--
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst, p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle, p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
--></style></head><body><div data-externalstyle="false" dir="ltr" style="font-family:Calibri,'Segoe UI',Meiryo,'Microsoft YaHei UI','Microsoft JhengHei UI','Malgun Gothic','Khmer UI','Nirmala UI',Tunga,'Lao UI',Ebrima,sans-serif;font-size:12pt;"><div>I was listening to Scott Meyers's talk at Going Native 2013 and it was mentioned that a warning about a call to std::move resulting in a copy instead of a move would cause so many false positives that it would be useless.</div><div> </div><div>Obviously it wouldn’t be useful to warn every time a return from std::move is copied, but maybe there is a subset that would be useful. My thoughts on what set of circumstances might lead to a useful warning.</div><div> </div><ol style="padding-top: 0px; padding-bottom: 0px; margin-top: 0px; margin-bottom: 0px; list-style-type: decimal;" dir="ltr"><li><div style="margin-right: 0px;">Value returned from std::move is copied</div></li><li><div style="margin-right: 0px;">Value returned from std::move is movable</div></li><li><div style="margin-right: 0px;">Value returned from std::move is const qualified</div></li></ol><div style="margin-right: 0px;" dir="ltr"> </div><div style="margin-right: 0px;" dir="ltr">Is there other set of restrictions that might be needed to make this useful?</div></div></body></html>