VideoFrameBuffer: Make non-const data access explicit
VideoFrameBuffer: Make non-const data access explicit

VideoFrameBuffer currently has two overloaded data() functions for pixel access, one for const and one for non-const. Unfortunately, it will default to the non-const version, even when 'const scoped_refptr<VideoFrameBuffer>&' is used. This is a problem, because many subclasses use RTC_NOTREACHED() in the non-const version.

This CL makes the non-const version of data() explicit with a different, longer function name MutableData().

R=tommi@webrtc.org

Review URL: https://codereview.webrtc.org/1304143003 .

Cr-Original-Commit-Position: 972c6d2dc6dd5efdad1377c0d224e03eb8f276f7@{#9787}
Cr-Mirrored-From: https://chromium.googlesource.com/external/webrtc
Cr-Mirrored-Commit: 3318f984cd7f51d24da4726665c05f5f06f82e6d

sippet/talk,dcpang/fatline-libjingle,sippet/talk,dcpang/fatline-libjingle,dcpang/fatline-libjingle,sippet/talk,dcpang/fatline-libjingle,dcpang/fatline-libjingle,sippet/talk,sippet/talk