Gerald Squelart b099eab802 Bug 1488684 - Made nsIFrame-derived classes and some others 'final' where possible - r=dbaron ... All classes deriving from nsIFrame that did not have any subclasses themselves (at the time of writing this patch) have been marked with `final`. Some other Layout classes have also been made final, but this was opportunistic while working on nsIFrame subclasses, and is definitely not exhaustive, further patches welcome; refer to bug 1332680. Advantages of marking a class final include: - Allowing the compiler to devirtualize some method calls (i.e., calling virtual functions directly instead of going through the vtable), - Indicating that the class is not currently subclassed, - Preventing subclassing without being aware that this would remove the finalization benefits of the parent class. `final` does not signify that these classes should *never* be subclassed, this is left for developers to decide. Differential Revision: https://phabricator.services.mozilla.com/D5020 --HG-- extra : moz-landing-system : lando		2018-09-06 01:23:14 +00:00
..
moz.build	Bug 1487190 - Update bugzilla metadata in moz.build files to reflect Layout components reorganization in bug 1484408. r=heycam	2018-09-05 11:16:02 +00:00
PRenderFrame.ipdl
PVsync.ipdl
RenderFrameChild.cpp
RenderFrameChild.h
RenderFrameParent.cpp	Bug 1487020 - Do not reuse nsDisplayRemote if RenderFrameParent has been destroyed r=mattwoodrow	2018-08-31 21:08:01 +02:00
RenderFrameParent.h	Bug 1488684 - Made nsIFrame-derived classes and some others 'final' where possible - r=dbaron	2018-09-06 01:23:14 +00:00
VsyncChild.cpp
VsyncChild.h
VsyncParent.cpp
VsyncParent.h