Closed
Bug 1606187
Opened 5 years ago
Closed 5 years ago
Remove usage of nsAutoPtr in nsClassHashtable
Categories
(Core :: XPCOM, enhancement)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
mozilla74
Tracking | Status | |
---|---|---|
firefox74 | --- | fixed |
People
(Reporter: erahm, Assigned: erahm)
References
Details
Attachments
(3 files)
After bug 1241518, nsClassHashtable
will be the last remaining usage of nsAutoPtr
in xpcom/
. Ideally we'll convert it over to using UniquePtr
.
There are a couple of issues beyond just conversion:
nsBaseHashtable
expects implicit conversion fromUserDataType
toDataType
whichUniquePtr
intentionally does not support. For example theIterator
class expects this.nsBaseHashtable
expects implicit assignment fromUserDataType
toDataType
whichUniquePtr
intentionally does not support. For examplensBaseHashtable::Put
currently uses this.nsBaseHashtable::Remove
has an optional out param that hands out a movedDataType
, all callers that use that need to be updated to useUniquePtr
instead for the out param
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
Assignee | ||
Comment 3•5 years ago
|
||
Updated•5 years ago
|
Assignee: nobody → erahm
Status: NEW → ASSIGNED
Pushed by erahm@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/910c51f0c374
Part 1: Add a DataType conversion helper to nsBaseHashtable r=froydnj,KrisWright
https://hg.mozilla.org/integration/autoland/rev/e5a8dac17bba
Part 2a: Switch nsClassHashtable over to UniquePtr r=KrisWright,froydnj
https://hg.mozilla.org/integration/autoland/rev/416ad9bef391
Part 2b: Update users of nsClassHashtable to handle UniquePtr differences r=KrisWright,froydnj
Comment 5•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/910c51f0c374
https://hg.mozilla.org/mozilla-central/rev/e5a8dac17bba
https://hg.mozilla.org/mozilla-central/rev/416ad9bef391
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox74:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla74
You need to log in
before you can comment on or make changes to this bug.
Description
•