Closed
Bug 1045091
Opened 10 years ago
Closed 10 years ago
Fix some bad implicit constructors in gfx
Categories
(Core :: Graphics, defect)
Core
Graphics
Tracking
()
RESOLVED
FIXED
mozilla34
People
(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)
References
Details
Attachments
(1 file)
2.69 KB,
patch
|
bas.schouten
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Attachment #8463434 -
Flags: review?(bgirard)
Comment 2•10 years ago
|
||
Comment on attachment 8463434 [details] [diff] [review]
Fix some bad implicit constructors in gfx
Review of attachment 8463434 [details] [diff] [review]:
-----------------------------------------------------------------
This looks fine but you're going to break the standalone moz2d build so forwarding to bas.
Attachment #8463434 -
Flags: review?(bgirard) → review?(bas)
Assignee | ||
Comment 3•10 years ago
|
||
(In reply to Benoit Girard (:BenWa) from comment #2)
> This looks fine but you're going to break the standalone moz2d build so
> forwarding to bas.
No, I'm not. MOZ_IMPLICIT is defined in mfbt/Attributes.h, which is included in the standalone moz2d builds as well.
Comment 4•10 years ago
|
||
Comment on attachment 8463434 [details] [diff] [review]
Fix some bad implicit constructors in gfx
Review of attachment 8463434 [details] [diff] [review]:
-----------------------------------------------------------------
As far as I can tell MOZ_IMPLICIT is defined inside MFBT so it should be fine for the stand-alone build. (Well, I need to update MFBT since it's new but that's a default part of my merging routine so that's fine) Any reason you think this will break the stand-alone build? As far as I can tell this is fine. Not that I shouldn't probably be reviewing this anyway :).
Attachment #8463434 -
Flags: review?(bas) → review+
Assignee | ||
Comment 5•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
You need to log in
before you can comment on or make changes to this bug.
Description
•