Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(603)

Issues Search
    My Issues | Starred     Open | Closed | All

Unified Diff: chrome/browser/chrome_thread.h

Issue 345037: Fifth patch in getting rid of caching MessageLoop pointers. (Closed) Base URL: svn://chrome-svn/chrome/trunk/src/
Patch Set: '' Created 11 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« chrome/browser/browsing_data_remover.h ('K') | « chrome/browser/browsing_data_remover.cc ('k') | chrome/browser/chrome_thread.cc » ('j') | chrome/browser/renderer_host/resource_dispatcher_host.cc » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: chrome/browser/chrome_thread.h
===================================================================
--- chrome/browser/chrome_thread.h (revision 30691)
+++ chrome/browser/chrome_thread.h (working copy)
@@ -113,12 +113,6 @@
// Callable on any thread. Returns whether you're currently on a particular
// thread.
- //
- // WARNING:
- // When running under unit-tests, this will return true if you're on the
- // main thread and the thread ID you pass in isn't running. This is
- // normally the correct behavior because you want to ignore these asserts
- // unless you've specifically spun up the threads, but be mindful of it.
static bool CurrentlyOn(ID identifier);
// If the current message loop is one of the known threads, returns true and
« chrome/browser/browsing_data_remover.h ('K') | « chrome/browser/browsing_data_remover.cc ('k') | chrome/browser/chrome_thread.cc » ('j') | chrome/browser/renderer_host/resource_dispatcher_host.cc » ('J')

Powered by Google App Engine
This is Rietveld 408576698