- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 63 for probes (0.17 sec)
-
guava/src/com/google/common/base/Stopwatch.java
import java.time.Duration; import java.util.concurrent.TimeUnit; /** * An object that accurately measures <i>elapsed time</i>: the measured duration between two * successive readings of "now" in the same process. * * <p>In contrast, <i>wall time</i> is a reading of "now" as given by a method like * {@link System#currentTimeMillis()}, best represented as an {@link java.time.Instant}. Such values
Java - Registered: Fri Apr 05 12:43:09 GMT 2024 - Last Modified: Thu Feb 23 15:09:35 GMT 2023 - 9.2K bytes - Viewed (0) -
android/guava/src/com/google/common/cache/Cache.java
* for an RPC may wait for a similar call that requests a long timeout, or a call by an * unprivileged user may return a resource accessible only to a privileged user making a similar * call. To prevent this problem, create a key object that includes all values that affect the * result of the query. Or use {@code LoadingCache.get(K)}, which lacks the ability to refer to * state other than that in the key. *
Java - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Sun Aug 07 02:38:22 GMT 2022 - 8.3K bytes - Viewed (0) -
guava-gwt/test/com/google/common/testing/Testing.gwt.xml
</source> <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package; see https://goo.gl/pRV3Yn for details. The summary is that it ignores one file in favor of the other.
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.5K bytes - Viewed (0) -
guava-gwt/src/com/google/common/xml/Xml.gwt.xml
</source> <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package; see https://goo.gl/pRV3Yn for details. The summary is that it ignores one file in favor of the other.
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.5K bytes - Viewed (0) -
android/guava/src/com/google/common/base/NullnessCasts.java
* nullness analysis might not understand that the field has been populated. To avoid that problem * without having to add {@code @SuppressWarnings}, the code can call this method. * * <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
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) -
android/guava/src/com/google/common/collect/ImmutableMultisetGwtSerializationDependencies.java
* * <p>For {@code ImmutableMultiset} in particular, I ran into a problem with the {@code * GwtSerializationDependencies} approach: When autogenerating a serializer for the new class, GWT * tries to refer to our dummy serializer for the superclass, * ImmutableMultiset_CustomFieldSerializer. But that type has no methods (since it's never actually * used). We could probably fix the problem by adding dummy methods to that class, but that is
Java - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Tue Jun 01 22:07:10 GMT 2021 - 1.9K bytes - Viewed (0) -
android/guava/src/com/google/common/util/concurrent/TimeoutFuture.java
* call cancel() and be unable to cancel the delegate. * There are a number of ways to solve this, none of which are very pretty, and it is currently * believed to be a purely theoretical problem (since the other actions should supply sufficient * write-barriers). */ @CheckForNull @LazyInit private ListenableFuture<V> delegateRef; @CheckForNull @LazyInit private ScheduledFuture<?> timer;
Java - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Feb 01 21:46:34 GMT 2024 - 7.7K bytes - Viewed (0) -
README.md
`@Deprecated` APIs will remain (again, unless they are `@Beta`). We have no plans to start removing things again, but officially, we're leaving our options open in case of surprises (like, say, a serious security problem). 3. Guava has one dependency that is needed for linkage at runtime: `com.google.guava:failureaccess:1.0.2`. It also has [some annotation-only dependencies][guava-deps], which we discuss in more
Plain Text - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Wed May 01 18:44:57 GMT 2024 - 5.9K bytes - Viewed (0) -
guava-gwt/src/com/google/thirdparty/publicsuffix/PublicSuffixType.gwt.xml
</source> <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package; see https://goo.gl/pRV3Yn for details. The summary is that it ignores one file in favor of the other.
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.4K bytes - Viewed (0) -
guava-gwt/src/com/google/common/base/Base.gwt.xml
</source> <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package; see https://goo.gl/pRV3Yn for details. The summary is that it ignores one file in favor of the other.
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.4K bytes - Viewed (0)