ThreadScope concept to check variable accessed on correct thread

ThreadScope concept to check variable accessed on correct thread
half-runtime, mostly compile-time


COMMIT=false
R=tommi@webrtc.org,pbos@webrtc.org

[tommi, 2016-05-12 09:39:12]

On 2016/05/11 17:31:08, danilchap wrote:

What to you think about making rtc::ThreadChecker lockable instead and have a
utility class that DCHECKs CalledOnValidThread?
(in addition to calling a noop unlock function)

[danilchap, 2016-05-12 11:04:55]

On 2016/05/12 09:39:12, tommi-webrtc wrote:
> On 2016/05/11 17:31:08, danilchap wrote:
> 
> What to you think about making rtc::ThreadChecker lockable instead and have a
> utility class that DCHECKs CalledOnValidThread?
> (in addition to calling a noop unlock function)

making rtc::ThreadChecker lockable would allow to test any thread, not just
rtc::Thread,
but I do not see a reason do do it 'instead': ThreadScope can easily do both
(sample uploaded).

[danilchap, 2016-05-12 16:02:10]

Description was changed from

==========
ThreadScope concept to check variable accessed on correct thread
half-runtime, mostly compile-time


COMMIT=false
R=tommi@webrtc.org,pbos@webrtc.org
==========

to

==========
ThreadScope concept to check variable accessed on correct thread
half-runtime, mostly compile-time


COMMIT=false
R=tommi@webrtc.org,pbos@webrtc.org
==========

[danilchap, 2016-05-12 16:02:10]

danilchap@webrtc.org changed reviewers:
- pbos@webrtc.org, tommi@webrtc.org