Custom scoping objects should have move support, act like std::unique_ptr<> in general |
|||||
Issue descriptionWe can't pass around a ScopedCreateDC object the way we can a unique_ptr, which means that functions that create DCs rely on the user manually calling DeleteDC(). Is this worth adding?
,
Jun 23 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 24 2017
,
Jun 25 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 25 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by pkasting@chromium.org
, Jun 22 2016Status: Available (was: Untriaged)
Summary: Custom scoping objects should have move support, act like std::unique_ptr<> in general (was: ScopedCreateDC might benefit from move support?)