* We overload this because we want readAndXWireFormat to
     * read the parameter words and bytes. This is so when
     * commands are batched together we can recursivly call
     * readAndXWireFormat without reading the non-existent header.
     */

    @Override
    int decode(final byte[] buffer, int bufferIndex) {
        final int start = headerStart = bufferIndex;

        bufferIndex += readHeaderWireFormat(buffer, bufferIndex);

        // Both have null netName
        assertTrue(info1.equals(info2));

        SmbShareInfo info3 = new SmbShareInfo(TEST_NET_NAME, 0, TEST_REMARK);
        // One null, one non-null
        assertFalse(info1.equals(info3));
        assertFalse(info3.equals(info1));
    }

    @Test
    @DisplayName("Test equals method with same object")
    void testEqualsWithSameObject() {

    void testHasMoreElements() {
        // Test initial state
        assertTrue(response.hasMoreElements());

        // Test after setting error code (not status)
        response.setTestErrorCode(1); // Non-zero errorCode indicates error
        assertFalse(response.hasMoreElements());

        // Reset error and test hasMore flag
        response.setTestErrorCode(0);
        response.hasMore = false;

                      &FloatDeallocator, nullptr);
}

// All the *Helper methods are used as a workaround for the restrictions that
// one cannot call ASSERT_* methods in non-void-returning functions (when
// exceptions are disabled during compilation)
void PlaceholderHelper(TF_Graph* graph, TF_Status* s, const char* name,
                       TF_DataType dtype, const std::vector<int64_t>& dims,

		31: {
			IsTruncated: false,
			Objects: []ObjectInfo{
				{Name: "obj1"},
				{Name: "obj2"},
				{Name: "temporary/0/"},
			},
		},
		// ListObjectsResult-32 Empty directory, non recursive listing
		32: {
			IsTruncated: false,
			Objects: []ObjectInfo{
				{Name: "obj1"},
				{Name: "obj2"},
			},
			Prefixes: []string{"temporary/"},
		},

        String[] result = JvmUtil.filterJvmOptions(new String[] { "8-:-Xmx1g", "9-:-Xmx2g" });
        assertEquals(1, result.length);
        assertEquals("-Xmx1g", result[0]);

        // Test with Java 9 (first non-1.x version)
        System.setProperty("java.version", "9.0.4");
        result = JvmUtil.filterJvmOptions(new String[] { "8-:-Xmx1g", "9-:-Xmx2g", "10-:-Xmx3g" });
        assertEquals(2, result.length);

    for (int p : NONZERO_INTEGER_CANDIDATES) {
      for (int q : NONZERO_INTEGER_CANDIDATES) {
        for (RoundingMode mode : ALL_SAFE_ROUNDING_MODES) {
          // Skip some tests that fail due to GWT's non-compliant int implementation.
          // TODO(cpovirk): does this test fail for only some rounding modes or for all?
          if (p == -2147483648 && q == -1 && intsCanGoOutOfRange()) {
            continue;
          }

        assertTrue(ex.getMessage().contains("Malformed Kerberos Ticket"));
    }

    @Test
    @DisplayName("byte[] ctor: top-level non-SEQUENCE triggers PACDecodingException (type mismatch)")
    void byteArrayConstructor_topLevelNotSequence_throws() throws Exception {
        // Arrange: Encoded INTEGER instead of SEQUENCE

            } else {

                /* On NT without Unicode the fileNameLength
                 * includes the '\0' whereas on win98 it doesn't. I
                 * guess most clients only support non-unicode so
                 * they don't run into this.
                 */

                /* UPDATE: Maybe not! Could this be a Unicode alignment issue. I hope

如果你宣告了回傳型別，FastAPI 會用它來進行資料的**驗證**、在 OpenAPI 中**文件化**、**過濾**，並使用 Pydantic 進行**序列化**。

/// tip

由於 Pydantic 會在 **Rust** 端進行序列化，宣告回傳型別可獲得比未宣告時高得多的**效能**。

///

### 非 async 的*路徑操作函式* { #non-async-path-operation-functions }

你也可以用一般的 `def` 函式（沒有 `async`），同樣用 `yield`。

FastAPI 會確保正確執行，不會阻塞事件迴圈。

因為這種情況下函式不是 async，正確的回傳型別會是 `Iterable[Item]`：