- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 405 for Like (0.17 sec)
-
guava-tests/test/com/google/common/base/PackageSanityTests.java
/** Basic sanity tests for classes in {@code common.base}. */ @GwtIncompatible public class PackageSanityTests extends AbstractPackageSanityTests { public PackageSanityTests() { // package private classes like FunctionalEquivalence are tested through the public API. publicApiOnly(); }
Java - Registered: Fri Apr 19 12:43:09 GMT 2024 - Last Modified: Tue Oct 10 08:40:05 GMT 2023 - 1K bytes - Viewed (0) -
android/guava/src/com/google/common/util/concurrent/AbstractExecutionThreadService.java
/** * Base class for services that can implement {@link #startUp}, {@link #run} and {@link #shutDown} * methods. This class uses a single thread to execute the service; consider {@link AbstractService} * if you would like to manage any threading manually. * * @author Jesse Wilson * @since 1.0 */ @GwtIncompatible @J2ktIncompatible @ElementTypesAreNonnullByDefault
Java - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Wed Dec 13 19:45:20 GMT 2023 - 7.6K bytes - Viewed (0) -
guava-gwt/src/com/google/common/io/Io.gwt.xml
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. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. However, unlike our other packages, as of this writing it has test supersource but no prod supersource.
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/math/Math.gwt.xml
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. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. However, unlike our other packages, as of this writing it has test supersource but no prod supersource.
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/thirdparty/publicsuffix/PublicSuffixPatterns.gwt.xml
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. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. However, unlike our other packages, as of this writing it has test supersource but no prod supersource.
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/src/com/google/common/collect/ImmutableMultisetGwtSerializationDependencies.java
* used). We could probably fix the problem by adding dummy methods to that class, but that is * starting to sound harder than taking the superclass approach, which I've been coming to like, * anyway, since it doesn't require us to declare dummy methods (though occasionally constructors) * and make types non-final. */ @GwtCompatible(emulated = true) @ElementTypesAreNonnullByDefault
Java - Registered: Fri Apr 05 12:43:09 GMT 2024 - Last Modified: Tue Jun 01 22:07:10 GMT 2021 - 1.9K bytes - Viewed (0) -
guava-gwt/src/com/google/common/net/Net.gwt.xml
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. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. However, unlike our other packages, as of this writing it has test supersource but no prod supersource.
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.7K bytes - Viewed (0) -
guava-gwt/test/com/google/common/collect/testing/Testing.gwt.xml
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. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. However, unlike our other packages, as of this writing it has test supersource but no prod supersource.
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.6K bytes - Viewed (0) -
android/guava/src/com/google/common/collect/ForwardingIterator.java
* default} methods. Specifically, it forwards calls only for methods that existed <a * href="https://docs.oracle.com/javase/7/docs/api/java/util/Iterator.html">before {@code default} * methods were introduced</a>. For newer methods, like {@code forEachRemaining}, it inherits their * default implementations. When those implementations invoke methods, they invoke methods on the * {@code ForwardingIterator}. * * @author Kevin Bourrillion * @since 2.0 */
Java - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Tue Jun 29 19:42:21 GMT 2021 - 2.2K bytes - Viewed (0) -
android/guava-tests/test/com/google/common/util/concurrent/TestThread.java
* test with reference to the same "lock-like object", and then their interactions with that object * are choreographed via the various methods on this class. * * <p>A "lock-like object" is really any object that may be used for concurrency control. If the * {@link #callAndAssertBlocks} method is ever called in a test, the lock-like object must have a
Java - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Wed Apr 26 20:07:17 GMT 2023 - 10.9K bytes - Viewed (0)