A few classes were marked as NS_FINAL_CLASS, but it turned out that after static analysis stopped happening, nsDerivedSafe got readded to nsCOMPtr and nsRefPtr, and then some of those "final" classes suddenly became base classes of particular specializations of nsCOMPtr_base<T>::nsDerivedSafe. MOZ_FINAL replaces NS_FINAL_CLASS, and unlike that macro it actually has teeth in the compilers developers will run with. Classes that wrongly used NS_FINAL_CLASS have had it removed for now. In the longer run, however, we should either have a final-but-for-nsDerivedSafe annotation/analysis, or we should remove nsDerivedSafe. bsmedberg in bug 704127 comment 5 also suggests maybe removing nsDerivedSafe from nsRefPtr alone might be a reasonable way to address this, and to maybe permit those classes to be MOZ_FINAL. dbaron thinks the remove-nsDerivedSafe/not-mark-those-classes-as-MOZ_FINAL question is a close one. I'll let people here fight it out, or something. :-)

Those few classes were the ones listed in bug 704127 comment 0, and which were changed in the obvious way in this commit: https://hg.mozilla.org/integration/mozilla-inbound/rev/3edc79afc842

Comment on attachment 582948 [details] [diff] [review] Patch now that nsDerivedSafe is history r=dbaron