Closed GoogleCodeExporter closed 9 years ago
ScopedGeneric provides ScopedGeneric(RValue) but not operator=(RValue). This is
the same as upstream. I don’t see where it says in the ScopedGeneric
documentation that this is supposed to work.
I think that this is a reasonable request, but it would need to appear upstream
in order to bring it into mini_chromium, so for now it’s WontFix in this
project’s bug database.
Original comment by mark@chromium.org
on 10 Mar 2015 at 6:15
This is the documentation that led me to believe this should work:
https://code.google.com/p/chromium/codesearch#chromium/src/base/move.h&q=move.h&
sq=package:chromium&type=cs&l=111
Original comment by rsesek@chromium.org
on 10 Mar 2015 at 6:17
That example does show an operator=(RValue) being defined. Earlier in the
move.h documentation, it says that the class needs to define its own:
https://code.google.com/p/chromium/codesearch#chromium/src/base/move.h&q=move.h&
sq=package:chromium&type=cs&l=26
Original comment by mark@chromium.org
on 10 Mar 2015 at 6:19
Upstream ScopedGeneric does:
https://code.google.com/p/chromium/codesearch#chromium/src/base/scoped_generic.h
&sq=package:chromium&type=cs&l=87
Original comment by rsesek@chromium.org
on 10 Mar 2015 at 6:21
That’s a move constructor, not operator=. I thought we were talking about
operator=.
Original comment by mark@chromium.org
on 10 Mar 2015 at 6:23
Oh, I guess that' only the ctor and not operator=. Nevermind.
Original comment by rsesek@chromium.org
on 10 Mar 2015 at 6:23
mini_chromium’s move.h and scoped_generic.h are identical to the
upstream’s, except for some insignificant comment differences.
Original comment by mark@chromium.org
on 10 Mar 2015 at 6:24
https://code.google.com/p/chromium/issues/detail?id=453142
Original comment by rsesek@chromium.org
on 10 Mar 2015 at 6:35
https://codereview.chromium.org/997953002/ :
https://chromium.googlesource.com/chromium/mini_chromium/+/b3d221e85747409f1ffb0
81ff958a1df7eb6be29
Original comment by rsesek@chromium.org
on 11 Mar 2015 at 6:02
Original issue reported on code.google.com by
rsesek@chromium.org
on 9 Mar 2015 at 11:02