- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 550 for Every (0.19 sec)
-
guava-tests/test/com/google/common/cache/TestingCacheLoaders.java
throw e; } }; } /** Returns a {@link CacheLoader} that returns the key for every request. */ static <T> IdentityLoader<T> identityLoader() { return new IdentityLoader<T>(); } /** * Returns a {@code new Object()} for every request, and increments a counter for every request. * The count is accessible via {@link #getCount}. */
Java - Registered: Fri Mar 22 12:43:11 GMT 2024 - Last Modified: Wed May 09 15:17:25 GMT 2018 - 4.9K bytes - Viewed (0) -
android/guava-tests/test/com/google/common/cache/TestingCacheLoaders.java
throw e; } }; } /** Returns a {@link CacheLoader} that returns the key for every request. */ static <T> IdentityLoader<T> identityLoader() { return new IdentityLoader<T>(); } /** * Returns a {@code new Object()} for every request, and increments a counter for every request. * The count is accessible via {@link #getCount}. */
Java - Registered: Fri Mar 22 12:43:11 GMT 2024 - Last Modified: Thu Apr 06 12:56:11 GMT 2023 - 4.9K bytes - Viewed (0) -
.cm/javadoc_on_new_files.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique # within the file. We keep each automation (or very closely related group of automations) in
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 2.1K bytes - Viewed (0) -
.cm/lacks_tests.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique # within the file. We keep each automation (or very closely related group of automations) in
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 2.7K bytes - Viewed (0) -
.cm/estimated_time_to_review.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique # within the file. We keep each automation (or very closely related group of automations) in
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 2.1K bytes - Viewed (0) -
.cm/includes_todos.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique # within the file. We keep each automation (or very closely related group of automations) in
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 2.1K bytes - Viewed (0) -
.cm/complex_changes.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique # within the file. We keep each automation (or very closely related group of automations) in
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 1.7K bytes - Viewed (0) -
.cm/code_experts.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique # within the file. We keep each automation (or very closely related group of automations) in
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 2.2K bytes - Viewed (0) -
docs/contribute/concurrency.md
primary responsibility for any HTTP client is to efficiently manage network connections. Creating and establishing new connections require a fair amount of overhead and added latency. OkHttp will make every effort to reuse existing connections to avoid this overhead and added latency. Every OkHttpClient uses a connection pool. Its job is to maintain a reference to all open connections. When an HTTP request is started, OkHttp will attempt to reuse an existing connection from the pool. If there...
Plain Text - Registered: Fri Mar 22 11:42:09 GMT 2024 - Last Modified: Sun Feb 06 16:35:36 GMT 2022 - 7K bytes - Viewed (0) -
.cm/platform_labels.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique # within the file. We keep each automation (or very closely related group of automations) in
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 6.5K bytes - Viewed (0)