E `Field` do Pydantic retorna uma instância de `FieldInfo` também.

`Body` também retorna objetos de uma subclasse de `FieldInfo` diretamente. E tem outras que você verá mais tarde que são subclasses da classe `Body`.

    }

    public void test_clickLogQueue_initialization() {
        assertNotNull(searchLogHelper.clickLogQueue);
        assertTrue(searchLogHelper.clickLogQueue.isEmpty());
    }

    // Mock classes
    private static class MockFessConfig extends FessConfig.SimpleImpl {
        private static final long serialVersionUID = 1L;

        @Override
        public boolean isUserInfo() {
            return true;
        }

import org.jspecify.annotations.Nullable;

/**
 * Provides static methods for serializing collection classes.
 *
 * <p>This class assists the implementation of collection classes. Do not use this class to
 * serialize collections that are defined elsewhere.
 *
 * @author Jared Levy
 */
@GwtIncompatible
@J2ktIncompatible
final class Serialization {
  private Serialization() {}

  /**

    tests, either. This causes it to fail to find AtomicLongMapTest.

    Our workaround is to tell GWT that util.concurrent and all other packages
    have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

    tests, either. This causes it to fail to find AtomicLongMapTest.

    Our workaround is to tell GWT that util.concurrent and all other packages
    have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

    tests, either. This causes it to fail to find AtomicLongMapTest.

    Our workaround is to tell GWT that util.concurrent and all other packages
    have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

//// tab | Python 3.8+

* `List`
* `Tuple`
* `Set`
* `Dict`
* `Union`
* `Optional`
* ...and others.

////

### Classes as types { #classes-as-types }

You can also declare a class as the type of a variable.

Let's say you have a class `Person`, with a name:

{* ../../docs_src/python_types/tutorial010.py hl[1:3] *}

Then you can declare a variable to be of type `Person`:

/**
 * A future that, if it fails, may <i>optionally</i> provide access to the cause of the failure.
 *
 * <p>This class is used only for micro-optimization. Standard {@code Future} utilities benefit from
 * this optimization, so there is no need to specialize methods to return or accept this type
 * instead of {@code ListenableFuture}.
 *
 * <p>This class is GWT-compatible.
 *

    class HappyPath {
        @Test
        void acceptWithMockedFile() throws Exception {
            SmbFile mockFile = mock(SmbFile.class);
            when(mockFile.getPath()).thenReturn("/share/file.txt");
            assertTrue(ALWAYSACTIVE.accept(mockFile));
        }
    }

    @Nested
    @DisplayName("Invalid input – null file handling")
    class InvalidPath {
        @Test

    }

    // Test command list construction with target classes directory
    public void test_executeSuggestCreator_withTargetClassesDir() {
        createRequiredDirectories();
        File targetDir = new File(System.getProperty("user.dir"), "target");
        File targetClassesDir = new File(targetDir, "classes");
        targetClassesDir.mkdirs();

        mockProcessHelper.setExitValue(0);