- Sort Score
- Num 10 results
- Language All
Results 1 - 10 of 26 for memoize (0.05 seconds)
-
guava/src/com/google/common/base/Suppliers.java
* delegating calls until it returns valid data. * * <p>If {@code delegate} is an instance created by an earlier call to {@code memoize}, it is * returned directly. */ public static <T extends @Nullable Object> Supplier<T> memoize(Supplier<T> delegate) { if (delegate instanceof NonSerializableMemoizingSupplier || delegate instanceof MemoizingSupplier) { return delegate; }Created: Fri Apr 03 12:43:13 GMT 2026 - Last Modified: Tue Mar 31 21:24:28 GMT 2026 - 16.1K bytes - Click Count (0) -
android/guava/src/com/google/common/base/Suppliers.java
* delegating calls until it returns valid data. * * <p>If {@code delegate} is an instance created by an earlier call to {@code memoize}, it is * returned directly. */ public static <T extends @Nullable Object> Supplier<T> memoize(Supplier<T> delegate) { if (delegate instanceof NonSerializableMemoizingSupplier || delegate instanceof MemoizingSupplier) { return delegate; }Created: Fri Apr 03 12:43:13 GMT 2026 - Last Modified: Tue Mar 31 21:24:28 GMT 2026 - 16.1K bytes - Click Count (0) -
api/maven-api-core/src/main/java/org/apache/maven/api/services/Interpolator.java
return chain(List.of(functions)); } /** * Memoizes a given function that takes a String input and produces a String output. * This method creates a new function that caches the results of the original function, * improving performance for repeated calls with the same input. * * @param callback The original function to be memoized. It takes a String as input and returns a String.
Created: Sun Apr 05 03:35:12 GMT 2026 - Last Modified: Mon Jan 13 16:14:35 GMT 2025 - 6.9K bytes - Click Count (0) -
build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild/testcleanup/TestFilesCleanupService.kt
// Some providers for the report files (Japicmp) are not memoizable internally and require project services to be resolved. // That's why we have to manually resolve them at the right point in time and explicitly memoize the results fun resolve() { // This makes `lazy` store the resolved value file } }Created: Wed Apr 01 11:36:16 GMT 2026 - Last Modified: Wed Feb 11 11:05:07 GMT 2026 - 14.3K bytes - Click Count (1) -
android/guava/src/com/google/common/util/concurrent/AbstractService.java
break; case TERMINATED: case FAILED: throw new AssertionError(); } } private void enqueueFailedEvent(State from, Throwable cause) { // can't memoize this one due to the exception listeners.enqueue( new ListenerCallQueue.Event<Listener>() { @Override public void call(Listener listener) { listener.failed(from, cause);Created: Fri Apr 03 12:43:13 GMT 2026 - Last Modified: Wed Feb 19 21:24:11 GMT 2025 - 20.3K bytes - Click Count (0) -
impl/maven-cli/src/main/java/org/apache/maven/cling/extensions/ExtensionConfigurationModule.java
if (configuration == null) { configuration = XmlNode.newInstance("configuration"); } UnaryOperator<String> cb = Interpolator.memoize(callback); UnaryOperator<String> it = s -> interpolator.interpolate(s, cb); configuration = new ExtensionInterpolator(it).transform(configuration); binder.bind(XmlNode.class)
Created: Sun Apr 05 03:35:12 GMT 2026 - Last Modified: Tue Mar 25 09:45:07 GMT 2025 - 2.9K bytes - Click Count (0) -
compat/maven-embedder/src/main/java/org/apache/maven/cli/ExtensionConfigurationModule.java
if (configuration == null) { configuration = XmlNode.newInstance("configuration"); } UnaryOperator<String> cb = Interpolator.memoize(callback); UnaryOperator<String> it = s -> interpolator.interpolate(s, cb); configuration = new ExtensionInterpolator(it).transform(configuration); binder.bind(XmlNode.class)
Created: Sun Apr 05 03:35:12 GMT 2026 - Last Modified: Tue Mar 25 09:45:07 GMT 2025 - 2.9K bytes - Click Count (0) -
docs/fr/docs/deployment/concepts.md
### Mémoire par processus { #memory-per-process } Maintenant, lorsque le programme charge des choses en mémoire, par exemple, un modèle de machine learning dans une variable, ou le contenu d'un gros fichier dans une variable, tout cela **consomme une partie de la mémoire (RAM)** du serveur.Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 19 18:37:13 GMT 2026 - 21.4K bytes - Click Count (0) -
docs/fr/docs/advanced/stream-data.md
Vous pouvez également l'utiliser pour diffuser de gros fichiers binaires, en envoyant chaque bloc de données au fur et à mesure de la lecture, sans tout charger en mémoire d'un coup. Vous pouvez aussi diffuser de la **vidéo** ou de l'**audio** de cette manière ; cela peut même être généré au fil du traitement et de l'envoi.
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 19 18:33:45 GMT 2026 - 6.2K bytes - Click Count (0) -
docs/fr/docs/deployment/docker.md
* Mémoire * Étapes préalables au démarrage ## Mémoire { #memory } Si vous exécutez **un seul processus par conteneur**, vous aurez une quantité de mémoire consommée plus ou moins bien définie, stable et limitée par chacun de ces conteneurs (plus d'un s'ils sont répliqués).Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 19 18:37:13 GMT 2026 - 32.3K bytes - Click Count (0)