- Sort Score
- Num 10 results
- Language All
Results 1 - 3 of 3 for enterXXX (0.03 seconds)
-
android/guava-tests/test/com/google/common/util/concurrent/GeneratedMonitorTest.java
import org.jspecify.annotations.Nullable; /** * Generated tests for {@link Monitor}. * * <p>This test class generates all of its own test cases in the {@link #suite()} method. Every * {@code enterXxx}, {@code tryEnterXxx}, and {@code waitForXxx} method of the {@code Monitor} class * is analyzed reflectively to determine appropriate test cases based on its signature. AdditionalCreated: Fri Apr 03 12:43:13 GMT 2026 - Last Modified: Mon Mar 16 22:45:21 GMT 2026 - 26.7K bytes - Click Count (0) -
guava-tests/test/com/google/common/util/concurrent/GeneratedMonitorTest.java
import org.jspecify.annotations.Nullable; /** * Generated tests for {@link Monitor}. * * <p>This test class generates all of its own test cases in the {@link #suite()} method. Every * {@code enterXxx}, {@code tryEnterXxx}, and {@code waitForXxx} method of the {@code Monitor} class * is analyzed reflectively to determine appropriate test cases based on its signature. AdditionalCreated: Fri Apr 03 12:43:13 GMT 2026 - Last Modified: Mon Mar 16 22:45:21 GMT 2026 - 26.7K bytes - Click Count (0) -
android/guava/src/com/google/common/util/concurrent/Monitor.java
// places you'll have monitor.enter()/monitor.leave() and other // places you'll have guard.enter()/guard.leave() even though // it's the same lock being acquired underneath. Always using // monitor.enterXXX()/monitor.leave() will make it really clear // which lock is held at any point in the code. // // 3. I think "enterWhen(notEmpty)" reads better than "notEmpty.enter()". //
Created: Fri Apr 03 12:43:13 GMT 2026 - Last Modified: Wed Jan 28 22:39:02 GMT 2026 - 43.5K bytes - Click Count (0)