Closed
Bug 1095117
Opened 8 years ago
Closed 8 years ago
move ImplCycleCollection{Unlink,Traverse} specializations for nsRefPtr out of nsRefPtr.h
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
mozilla36
People
(Reporter: froydnj, Assigned: froydnj)
Details
Attachments
(1 file)
1.23 KB,
patch
|
mccr8
:
review+
|
Details | Diff | Splinter Review |
I don't particularly care where they go (new header seems like the best option?), but it seems silly to have nsRefPtr.h drag in all the cycle collection machinery all the time. Not all clients of nsRefPtr will need these specializations, and clients that do should be forced to include whatever headers they need.
![]() |
Assignee | |
Comment 1•8 years ago
|
||
Transferring these to another header was...unsuccessful, but some forward declarations are sufficient to untangle things (though it's possible that unified builds are just masking problems here).
Attachment #8518986 -
Flags: review?(continuation)
![]() |
Assignee | |
Updated•8 years ago
|
Assignee: nobody → nfroyd
Comment 2•8 years ago
|
||
Comment on attachment 8518986 [details] [diff] [review] forward-declare cycle collection things in nsRefPtr.h Review of attachment 8518986 [details] [diff] [review]: ----------------------------------------------------------------- thanks
Attachment #8518986 -
Flags: review?(continuation) → review+
![]() |
Assignee | |
Comment 3•8 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/818ef4dc2697
Flags: in-testsuite-
Comment 4•8 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/818ef4dc2697
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla36
You need to log in
before you can comment on or make changes to this bug.
Description
•