DescriptionVideoFrameBuffer: 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
Committed: https://chromium.googlesource.com/external/webrtc/+/3318f984cd7f51d24da4726665c05f5f06f82e6d
Patch Set 1 : #Patch Set 2 : Rebase #
Messages
Total messages: 15 (6 generated)
|