Lines Matching refs:one
3 // Mutex<Vec<T>>. It has one small trick: because unlocking a mutex is somewhat
42 // there are at least some use case patterns where one might have many threads
43 // sitting around that might have used a regex at one point. While thread_local
72 // thread ID might result in more than one thread "owning" a pool,
88 /// empty and the caller requests one.
99 /// guaranteed to provide a value to exactly one thread at any time.
137 // The key is to guarantee that 'owner_val' can only ever be accessed from one
140 // that created the Pool. Since this can only ever be one thread, it follows
141 // that only one thread can access 'owner_val' at any point in time. Thus, it
202 // SAFETY: We must guarantee that only one thread gets access to this
205 // owner, then only one thread may receive this value.
322 // If we didn't implement the single owner optimization, then one of