Closed
Bug 1447454
Opened 6 years ago
Closed 6 years ago
Stop allowing implicit downcasts in StrongOrRawPtr
Categories
(Core :: DOM: Core & HTML, enhancement, P2)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla61
Tracking | Status | |
---|---|---|
firefox61 | --- | fixed |
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
Details
Attachments
(1 file)
2.78 KB,
patch
|
peterv
:
review+
|
Details | Diff | Splinter Review |
Given the way the StrongOrRawPtr(already_AddRefed<S>&& aPtr) ctor does a downcast, you can do things like: interface Foo { Element bar(); }; and then have Foo::bar() return already_AddRefed<nsINode> and this will compile. This is obviously not good. ;) Luckily we have only two things that are relying on this behavior, and both are actually safe. One is being removed in bug 1446246 and the other is simple to fix.
Assignee | ||
Comment 1•6 years ago
|
||
Attachment #8960780 -
Flags: review?(peterv)
Updated•6 years ago
|
Priority: -- → P2
Updated•6 years ago
|
Attachment #8960780 -
Flags: review?(peterv) → review+
Assignee | ||
Comment 2•6 years ago
|
||
Bug 888600 introduced new failures of this sort, but I think bug 1448850 will remove them again....
Depends on: 1448850
Pushed by bzbarsky@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/5cc5f9c978a3 Stop allowing implicit downcasts in StrongOrRawPtr. r=peterv
Comment 4•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/5cc5f9c978a3
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox61:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•