// @Ignore affects the Android test runner, which respects JUnit 4 annotations on JUnit 3 tests.
@SuppressWarnings("JUnit4ClassUsedInJUnit3")
@IgnoreJRERequirement // We opt into library desugaring for our tests.
public class MapMergeTester<K, V> extends AbstractMapTester<K, V> {
  @MapFeature.Require(SUPPORTS_PUT)
  public void testAbsent() {
    assertEquals(
        "Map.merge(absent, value, function) should return value",
        v3(),

  @Override
  public <T extends @NonNull B> @Nullable T getInstance(Class<T> type) {
    return trustedGet(TypeToken.of(type));
  }

  @Override
  public <T extends @NonNull B> @Nullable T getInstance(TypeToken<T> type) {
    return trustedGet(type.rejectTypeVariables());
  }

  @Override
  @CanIgnoreReturnValue
  public <T extends B> @Nullable T putInstance(
      Class<@NonNull T> type, @ParametricNullness T value) {

import junit.framework.TestCase;
import org.jspecify.annotations.NullMarked;
import org.jspecify.annotations.Nullable;

/** Test case for {@link TrustedListenableFutureTask}. */
@NullMarked
@GwtCompatible
public class TrustedListenableFutureTaskTest extends TestCase {

  public void testSuccessful() throws Exception {
    TrustedListenableFutureTask<Integer> task = TrustedListenableFutureTask.create(returning(2));

# Geschichte, Design und Zukunft

Vor einiger Zeit fragte <a href="https://github.com/fastapi/fastapi/issues/3#issuecomment-454956920" class="external-link" target="_blank">ein **FastAPI**-Benutzer</a>:

> Was ist die Geschichte dieses Projekts? Es scheint, als wäre es in ein paar Wochen aus dem Nichts zu etwas Großartigem geworden [...]

Hier ist ein wenig über diese Geschichte.

## Alternativen

# История создания и дальнейшее развитие

Однажды, <a href="https://github.com/fastapi/fastapi/issues/3#issuecomment-454956920" class="external-link" target="_blank">один из пользователей **FastAPI** задал вопрос</a>:

> Какова история этого проекта? Создаётся впечатление, что он явился из ниоткуда и завоевал мир за несколько недель [...]

Что ж, вот небольшая часть истории проекта.

## Альтернативы

O `TestClient` é baseado no <a href="https://www.python-httpx.org" class="external-link" target="_blank">HTTPX</a>, e felizmente nós podemos utilizá-lo diretamente para testar a API.

## Exemplo

 * It helps maintain the search index by cleaning up outdated content automatically.
 */
public class PurgeDocJob {

    /** Logger instance for this class */
    private static final Logger logger = LogManager.getLogger(PurgeDocJob.class);

    /**
     * Default constructor for PurgeDocJob.
     * Creates a new instance of the document purging job with default settings.
     */

/**
 * A dictionary creator for stemmer override files.
 * This class is responsible for creating {@link StemmerOverrideFile} instances
 * from files that match the pattern "stemmer_override.*\\.txt".
 */
public class StemmerOverrideCreator extends DictionaryCreator {
    private static final Logger logger = LogManager.getLogger(StemmerOverrideCreator.class);

    /**
     * Constructs a new creator for stemmer override dictionaries.

        // Test that the log method exists and can be called
        // We can't easily test the actual functionality without complex mocking
        // but we can verify the class structure
        assertNotNull(crawlerLogHelper);
        assertTrue(CrawlerLogHelper.class.getSuperclass().getSimpleName().contains("LogHelper"));
    }

import org.codelibs.fess.app.web.admin.dict.kuromoji.EditForm;

/**
 * Request body class for Kuromoji dictionary edit operations in the admin REST API.
 * This class extends EditForm to inherit the necessary form validation and binding capabilities
 * for Kuromoji dictionary management operations.
 */
public class EditBody extends EditForm {

    /**
     * Default constructor.
     */
    public EditBody() {