So to be clear, it is often not truly about using the value after it is moved. It is about expecting that the variable / member has been nulled out after moving it. If I WTFMove() out a data member m_dataMember, I expect later on `if (m_dataMember)` to be false.
-- Chris Dumez > On Dec 14, 2018, at 3:45 PM, Chris Dumez <cdu...@apple.com> wrote: > > >> On Dec 14, 2018, at 3:39 PM, Fujii Hironori <fujii.hiron...@gmail.com >> <mailto:fujii.hiron...@gmail.com>> wrote: >> >> >> On Sat, Dec 15, 2018 at 6:38 AM Chris Dumez <cdu...@apple.com >> <mailto:cdu...@apple.com>> wrote: >> >> I have now been caught twice by std::optional’s move constructor. >> >> I don't understand how this could be useful? Do you want to use the value >> after it is moved? I'd like to see these your code. Could you show me these >> two patches? > > This is the latest one: https://trac.webkit.org/changeset/239228/webkit > <https://trac.webkit.org/changeset/239228/webkit> > > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > https://lists.webkit.org/mailman/listinfo/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
