Make ImageFrame member getAddr() public
Created attachment 115046 [details] Patch
Comment on attachment 115046 [details] Patch The ChangeLog needs to explain why we're making this change.
Would something like https://bugs.webkit.org/show_bug.cgi?id=59670#c8 be enough?
Not really. Sure, we could make the function public, but why would we want to? As a general rule, we prefer to limit the visibility of functions. Unless there's a reason to make it public, we'll probably leave it private.
Ok, lemme better explain it then ...
Created attachment 115079 [details] Patch
Comment on attachment 115079 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=115079&action=review > Source/WebCore/ChangeLog:12 > + Make ImageFrame member getAddr() public to allow ImageFrame users access to the > + underlying frame pixels if needed. Image decoders, for example, could with care > + use this service to write decoded pixels direct to the ImageFrame pixel buffer, > + avoiding intermeadiate data copies from temporary decoded pixel row buffers and > + the decoding performance loss that that entails. Is there an example of an image decoder that would benefit from this API?
> Is there an example of an image decoder that would benefit from this API? libturbo-jpeg would be one example.
Comment on attachment 115079 [details] Patch Ok
Comment on attachment 115079 [details] Patch Clearing flags on attachment: 115079 Committed r100252: <http://trac.webkit.org/changeset/100252>
All reviewed patches have been landed. Closing bug.