- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 580 for mplacer (0.23 sec)
-
tensorflow/c/eager/parallel_device/parallel_device.cc
// We assume that any tensors already placed on this device are // ParallelTensors. typed_inputs.emplace_back(reinterpret_cast<ParallelTensor*>( TFE_TensorHandleDevicePointer(input, status))); if (TF_GetCode(status) != TF_OK) return; } else { typed_inputs.emplace_back(input); } }
C++ - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Wed Mar 29 22:05:31 GMT 2023 - 18.3K bytes - Viewed (0) -
api/maven-api-core/src/main/java/org/apache/maven/api/services/DependencyResolverResult.java
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Mar 01 17:18:13 GMT 2024 - 3.4K bytes - Viewed (0) -
api/maven-api-core/src/main/java/org/apache/maven/api/Type.java
/** * Artifact type name for a JAR file containing test classes. If the main artifact is placed on the class-path * ({@value #JAR} or {@value #CLASSPATH_JAR} types), then the test artifact will also be placed on the class-path. * Otherwise, if the main artifact is placed on the module-path ({@value #JAR} or {@value #MODULAR_JAR} types),
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Mar 29 09:32:19 GMT 2024 - 5.6K bytes - Viewed (0) -
maven-api-impl/src/main/java/org/apache/maven/internal/impl/DefaultDependencyResolverResult.java
* So the modular test output directory usually needs to be placed in a {@code --path-module} option. * * <ul> * <li>If the test output directory is modular, then: * <ul> * <li>If a test module name is identical to a main module name, * place the test directory in a {@code --patch-module} option.</li> * <li>Otherwise, place the test directory on the module-path. However, this case
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Mar 25 10:50:01 GMT 2024 - 14.2K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/internal/impl/PathModularizationCache.java
* * @param types types of path where a dependency can be placed * @param filter filter the paths accepted by the tool which will consume the path * @param path path to the JAR file or output directory of the dependency * @return where to place the dependency, or an empty value if the placement cannot be determined
Java - Registered: Sun Mar 24 03:35:10 GMT 2024 - Last Modified: Fri Mar 01 17:18:13 GMT 2024 - 5.2K bytes - Viewed (0) -
docs/en/docs/advanced/additional-responses.md
The correct place is: * In the key `content`, that has as value another JSON object (`dict`) that contains: * A key with the media type, e.g. `application/json`, that contains as value another JSON object, that contains: * A key `schema`, that has as the value the JSON Schema from the model, here's the correct place.
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Thu Jan 11 16:31:18 GMT 2024 - 8.8K bytes - Viewed (0) -
maven-api-impl/src/main/java/org/apache/maven/internal/impl/PathModularizationCache.java
* * @param types types of path where a dependency can be placed * @param filter filter the paths accepted by the tool which will consume the path * @param path path to the JAR file or output directory of the dependency * @return where to place the dependency, or an empty value if the placement cannot be determined
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Mar 25 10:50:01 GMT 2024 - 5.2K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/internal/impl/DefaultDependencyResolverResult.java
* So the modular test output directory usually needs to be placed in a {@code --path-module} option. * * <ul> * <li>If the test output directory is modular, then: * <ul> * <li>If a test module name is identical to a main module name, * place the test directory in a {@code --patch-module} option.</li> * <li>Otherwise, place the test directory on the module-path. However, this case
Java - Registered: Sun Mar 24 03:35:10 GMT 2024 - Last Modified: Fri Mar 01 17:18:13 GMT 2024 - 14.2K bytes - Viewed (0) -
api/maven-api-core/src/main/java/org/apache/maven/api/JavaPathType.java
* <p><b>Context-sensitive interpretation:</b> * A dependency with this path type will not necessarily be placed on the class-path. * There are two circumstances where the dependency may nevertheless be placed somewhere else: * </p> * <ul> * <li>If {@link #MODULES} path type is also set, then the dependency can be placed either on the * class-path or on the module-path, but only one of those. The choice is up to the plugin,
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Mar 01 17:18:13 GMT 2024 - 11.6K bytes - Viewed (0) -
docs/bucket/lifecycle/DESIGN.md
Lifecycle transition rules can be applied to buckets (both versioned and un-versioned) by specifying the tier name defined above as the transition storage class for the lifecycle rule. ## Implementation
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 4.3K bytes - Viewed (0)