Search Options

Results per page
Sort
Preferred Languages
Advance

Results 51 - 54 of 54 for composites (0.05 sec)

  1. okhttp/src/commonJvmAndroid/kotlin/okhttp3/HttpUrl.kt

     * "/square/okhttp/issues/1486" and decompose into a list of segments like `["square", "okhttp",
     * "issues", "1486"]`.
     *
     * This class offers methods to compose and decompose paths by segment. It composes each path
     * from a list of segments by alternating between "/" and the encoded segment. For example the
     * segments `["a", "b"]` build "/a/b" and the segments `["a", "b", ""]` build "/a/b/".
     *
    Registered: Fri Dec 26 11:42:13 UTC 2025
    - Last Modified: Mon May 05 16:01:00 UTC 2025
    - 63.5K bytes
    - Viewed (0)
  2. src/main/java/jcifs/smb1/smb1/SmbFile.java

        FileEntry[] doMsrpcShareEnum() throws IOException {
            MsrpcShareEnum rpc;
            DcerpcHandle handle;
    
            rpc = new MsrpcShareEnum(url.getHost());
    
            /* JCIFS will build a composite list of shares if the target host has
             * multiple IP addresses such as when domain-based DFS is in play. Because
             * of this, to ensure that we query each IP individually without re-resolving
    Registered: Sat Dec 20 13:44:44 UTC 2025
    - Last Modified: Sat Aug 30 05:58:03 UTC 2025
    - 112.2K bytes
    - Viewed (0)
  3. RELEASE.md

            This calling convention is now the preferred way to use concrete
            functions with nested values and composite tensors. Please check the
            [guide](https://www.tensorflow.org/guide/concrete_function) for more
            details on `concrete_ function`.
        *   Update `tf.function`'s `experimental_relax_shapes` to handle composite
            tensors appropriately.
        *   Optimize `tf.function` invocation, by removing redundant list converter.
    Registered: Tue Dec 30 12:39:10 UTC 2025
    - Last Modified: Tue Oct 28 22:27:41 UTC 2025
    - 740.4K bytes
    - Viewed (3)
  4. docs/en/docs/release-notes.md

        * Composite bodies' IDs are now based on path, not only on route name, as the auto-generated name uses the function names, that can be duplicated in different modules.
        * The same new ID generation applies to response models.
        * This also changes the generated title for those models.
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Sat Dec 27 19:06:15 UTC 2025
    - 586.7K bytes
    - Viewed (0)
Back to top