try {
      getChecked(ERROR_FUTURE, TwoArgConstructorException.class);
    } catch (Error expected) {
      assertEquals(ERROR, expected);
      return;
    }
    fail();
  }

  public void testGetCheckedUntimed_badExceptionConstructor_failsEvenForSuccessfulInput()
      throws Exception {
    assertThrows(
        IllegalArgumentException.class,

    try {
      getChecked(ERROR_FUTURE, TwoArgConstructorException.class);
    } catch (Error expected) {
      assertEquals(ERROR, expected);
      return;
    }
    fail();
  }

  public void testGetCheckedUntimed_badExceptionConstructor_failsEvenForSuccessfulInput()
      throws Exception {
    assertThrows(
        IllegalArgumentException.class,

    @Override
    protected Invoker createInvoker(ClassWorld classWorld) {
        return new MavenInvoker(
                ProtoLookup.builder().addMapping(ClassWorld.class, classWorld).build(), null);
    }

    @Override
    protected Parser createParser() {
        return new MavenParser();
    }

    @Test
    void defaultFs(
            @TempDir(cleanup = CleanupMode.ON_SUCCESS) Path cwd,

        assertSame(first, second);
        assertSame(invertibleCryptographer, first);
    }

    @Test
    public void test_providePrimaryInvertibleCryptographer_consistency() {
        // Test multiple calls return consistent results
        for (int i = 0; i < 10; i++) {
            InvertibleCryptographer cryptographer = securityResourceProvider.providePrimaryInvertibleCryptographer();
            assertNotNull(cryptographer);

    }
}

fun readCapabilities(source: File): List<CapabilitySpec> {
    JsonReader(source.reader(Charsets.UTF_8)).use { reader ->
        reader.strictness = Strictness.LENIENT
        return Gson().fromJson(reader)
    }
}

inline
fun <reified T> Gson.fromJson(json: JsonReader): T = this.fromJson(json, object : TypeToken<T>() {}.type)


abstract class CapabilityRule @Inject constructor(

因此，FastAPI 會負責（透過 Pydantic）過濾掉輸出模型中未宣告的所有資料。

### `response_model` 或回傳型別 { #response-model-or-return-type }

在這種情況下，因為兩個模型不同，如果我們把函式回傳型別註解為 `UserOut`，編輯器和工具會抱怨我們回傳了無效的型別，因為它們是不同的類別。

這就是為什麼在這個例子中我們必須在 `response_model` 參數中宣告它。

...但繼續往下讀看看如何克服這個問題。

## 回傳型別與資料過濾 { #return-type-and-data-filtering }

讓我們延續前一個範例。我們想要用一種型別來註解函式，但實際上希望能夠從函式回傳包含更多資料的內容。

// and as such incurred latencies.
var Discard io.Writer = discard{}

// discard is /dev/null for Golang.
type discard struct{}

func (discard) Write(p []byte) (int, error) {
	return len(p), nil
}

// DiscardReader discarded reader
func DiscardReader(r io.Reader) {
	Copy(Discard, r)

     * with parameters from the paramMap substituted into the template.
     *
     * @param template the template string to evaluate
     * @param paramMap the map of parameters to substitute into the template
     * @return the result of evaluating the template, or null if evaluation fails
     */
    Object evaluate(final String template, final Map<String, Object> paramMap);

    events.add(string);
  }

  public void methodWithoutAnnotation(@Nullable String string) {
    Assert.fail("Event bus must not call methods without @Subscribe!");
  }

  public List<String> getEvents() {
    return events;
  }

public interface ResourceNameFilter {

    /**
     * Tests whether the specified resource name should be included.
     *
     * @param parent the parent SMB resource
     * @param name the resource name to test
     * @return whether the given filename should be included
     * @throws CIFSException if an error occurs while accessing the resource
     */
    boolean accept(SmbResource parent, String name) throws CIFSException;