Closed
Bug 1053190
Opened 11 years ago
Closed 11 years ago
Reduce unnecessary inclusion of nsINode.h in headers
Categories
(Core :: DOM: Core & HTML, enhancement)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla34
People
(Reporter: ayg, Assigned: ayg)
References
Details
Attachments
(1 file)
|
18.07 KB,
patch
|
ehsan.akhgari
:
review+
|
Details | Diff | Splinter Review |
I sat around waiting for several minutes for Gecko to build after making a change to nsINode. I don't know how much this improves things, but it can't hurt.
| Assignee | ||
Comment 1•11 years ago
|
||
Attachment #8472331 -
Flags: review?(ehsan)
Comment 2•11 years ago
|
||
Comment on attachment 8472331 [details] [diff] [review]
Patch
Review of attachment 8472331 [details] [diff] [review]:
-----------------------------------------------------------------
Nice! (Please make sure this builds on all platforms on try...)
Attachment #8472331 -
Flags: review?(ehsan) → review+
| Assignee | ||
Comment 3•11 years ago
|
||
Try: https://tbpl.mozilla.org/?tree=Try&rev=aa8a1924d55e
https://hg.mozilla.org/integration/mozilla-inbound/rev/6030bd4e48f8
Flags: in-testsuite-
Comment 4•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
Comment 5•11 years ago
|
||
> Please make sure this builds on all platforms on try...
That should have been "in a non-unified build". Because the change to nsINodeList.h is wrong: it returns nsIContent* from methods that bindings expect to return nsINode*, so it needs to include nsIContent.h so that callers will see that nsIContent inherits from nsINode. It happened to build because of how the unified build stars aligned, but randomly broke other people's patches that didn't touch this code at all.
| Assignee | ||
Comment 6•11 years ago
|
||
Based on the errors I get on try, it looks like at least one or two of the platforms are building non-unified, and I did have to fix a number of errors that looked like non-unified-only errors. It might be that there was a platform-specific non-unified-only problem.
If includes are needed for non-obvious reasons, it's a good idea to explain why in a comment. Manual or semi-automated (iwyu) inclusion reduction will remove them otherwise, and I think removing unnecessary includes is considered a good thing, so chances are it might happen again.
Comment 7•11 years ago
|
||
(In reply to :Aryeh Gregor from comment #6)
> Based on the errors I get on try, it looks like at least one or two of the
> platforms are building non-unified, and I did have to fix a number of errors
> that looked like non-unified-only errors. It might be that there was a
> platform-specific non-unified-only problem.
Yeah, IIRC linux32 perhaps among others, which is why I suggested the try run... Sorry if this broke people's patches :(
Unable to verify, this seems to be a back end issue.
QA Whiteboard: [QAnalyst-verify-]
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-verify-] → [QAnalyst-Triage?][QAnalyst-verify-]
Flags: needinfo?(ktucker)
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?][QAnalyst-verify-] → [QAnalyst-Triage+][QAnalyst-verify-]
Flags: needinfo?(ktucker)
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•