- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 20 for Reeves (0.14 sec)
-
android/guava/src/com/google/common/util/concurrent/Monitor.java
* * <p>A call to any of the <i>enter</i> methods with <b>void</b> return type should always be * followed immediately by a <i>try/finally</i> block to ensure that the current thread leaves the * monitor cleanly: * * <pre>{@code * monitor.enter(); * try { * // do things while occupying the monitor * } finally { * monitor.leave(); * } * }</pre> *
Java - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Mon Dec 04 18:22:01 GMT 2023 - 38.6K bytes - Viewed (0) -
android/guava/src/com/google/common/util/concurrent/NullnessCasts.java
* * <p>Why <i>not</i> just add {@code SuppressWarnings}? The problem is that this method is * typically useful for {@code return} statements. That leaves the code with two options: Either * add the suppression to the whole method (which turns off checking for a large section of code), * or extract a variable, and put the suppression on that. However, a local variable typically
Java - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Feb 10 20:36:34 GMT 2022 - 3.9K bytes - Viewed (0) -
android/guava/src/com/google/common/util/concurrent/FluentFuture.java
* * <p>This method is similar to {@link java.util.concurrent.CompletableFuture#whenComplete} and * {@link java.util.concurrent.CompletableFuture#whenCompleteAsync}. It also serves the use case * of {@link java.util.concurrent.CompletableFuture#thenAccept} and {@link * java.util.concurrent.CompletableFuture#thenAcceptAsync}. *
Java - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Tue Apr 11 19:08:44 GMT 2023 - 18.7K bytes - Viewed (0) -
guava-tests/test/com/google/common/io/testdata/alice_in_wonderland.txt
seemed to rise like a stalk out of a sea of green leaves that lay far below her. `What CAN all that green stuff be?' said Alice. `And where HAVE my shoulders got to? And oh, my poor hands, how is it I can't see you?' She was moving them about as she spoke, but no result seemed to follow, except a little shaking among the distant green leaves. As there seemed to be no chance of getting her hands up to her
Plain Text - Registered: Fri Apr 12 12:43:09 GMT 2024 - Last Modified: Mon Oct 29 21:35:03 GMT 2012 - 145.2K bytes - Viewed (0) -
android/guava/src/com/google/common/collect/NullnessCasts.java
* * <p>Why <i>not</i> just add {@code SuppressWarnings}? The problem is that this method is * typically useful for {@code return} statements. That leaves the code with two options: Either * add the suppression to the whole method (which turns off checking for a large section of code), * or extract a variable, and put the suppression on that. However, a local variable typically
Java - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Thu Feb 10 20:36:34 GMT 2022 - 3.5K bytes - Viewed (0) -
guava/src/com/google/common/base/Optional.java
* * <p><b>Comparison to {@code java.util.Optional}:</b> this class leaves the specific choice of * hash code unspecified, unlike the Java 8+ equivalent. */ @Override public abstract int hashCode(); /** * Returns a string representation for this instance. * * <p><b>Comparison to {@code java.util.Optional}:</b> this class leaves the specific string
Java - Registered: Fri Apr 05 12:43:09 GMT 2024 - Last Modified: Mon Apr 01 16:15:01 GMT 2024 - 14.6K bytes - Viewed (0) -
android/guava/src/com/google/common/hash/HashFunction.java
* including those in many JDK classes. * * <p>{@code Object.hashCode} implementations tend to be very fast, but have weak collision * prevention and <i>no</i> expectation of bit dispersion. This leaves them perfectly suitable for * use in hash tables, because extra collisions cause only a slight performance hit, while poor bit * dispersion is easily corrected using a secondary hash function (which all reasonable hash table
Java - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Tue May 25 18:22:59 GMT 2021 - 10.9K bytes - Viewed (0) -
guava/src/com/google/common/cache/LocalCache.java
* ensure that completed write operations performed by other threads are noticed. For most * purposes, the "count" field, tracking the number of elements, serves as that volatile * variable ensuring visibility. This is convenient because this field needs to be read in many * read operations anyway: *
Java - Registered: Fri Apr 05 12:43:09 GMT 2024 - Last Modified: Thu Feb 22 17:40:56 GMT 2024 - 150.3K bytes - Viewed (0) -
android/guava/src/com/google/common/base/NullnessCasts.java
* * <p>Why <i>not</i> just add {@code SuppressWarnings}? The problem is that this method is * typically useful for {@code return} statements. That leaves the code with two options: Either * add the suppression to the whole method (which turns off checking for a large section of code), * or extract a variable, and put the suppression on that. However, a local variable typically
Java - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Tue Aug 17 15:44:29 GMT 2021 - 3.1K bytes - Viewed (0) -
guava-tests/test/com/google/common/util/concurrent/GeneratedMonitorTest.java
// (b) Waiting for the single guard to become satisfied. // (c) Occupying the monitor and awaiting the tearDownLatch. // // Except for (c), every thread should occupy the monitor very briefly, and every thread leaves // the monitor with the guard satisfied. Therefore as soon as tearDownLatch is triggered, we // should be able to enter the monitor, and then we set the guard to satisfied for the benefit
Java - Registered: Fri Apr 12 12:43:09 GMT 2024 - Last Modified: Mon Apr 17 14:48:57 GMT 2023 - 27.4K bytes - Viewed (0)