* calling {@code get(columnKey, rowKey)} on the generated table always returns the same value as
   * calling {@code get(rowKey, columnKey)} on the original table. Updating the original table
   * changes the contents of the transposed table and vice versa.
   *
   * <p>The returned table supports update operations as long as the input table supports the

    ContainsBothWithMultisetFirst reMultisetFirst = reserialize(multisetFirst);
    assertThat(reMultisetFirst.a.isEmpty()).isFalse();
    // The following NPE is a side effect of our changes to avoid mutating `final` fields.
    assertThrows(NullPointerException.class, () -> reMultisetFirst.z.multiset.isEmpty());

    ContainsBothWithContainsMultisetFirst reContainsMultisetFirst =

import org.codelibs.core.exception.IORuntimeException;

/**
 * The {@code DynamicProperties} class extends {@link Properties} to provide dynamic
 * loading and storing of properties from a file. It monitors the file for changes
 * and reloads the properties if the file is updated. This class is thread-safe and
 * ensures that the properties are always up-to-date.
 *
 * <p>Key Features:
 * <ul>

        if (getMojos() == null) {
            return null; // no mojo in this POM
        }

        // TODO could we use a map? Maybe if the parent did that for components too, as this is too vulnerable to
        // changes above not being propagated to the map
        for (MojoDescriptor desc : getMojos()) {
            if (goal.equals(desc.getGoal())) {
                return desc;
            }
        }
        return null;

import org.opensearch.action.admin.indices.alias.get.GetAliasesResponse;
import org.opensearch.action.admin.indices.create.CreateIndexResponse;
import org.opensearch.transport.client.Client;

/**
 * Test class for refactoring changes made to Suggester class.
 *
 * Tests cover:
 * - Index alias helper method (getIndicesForAlias)
 * - Edge cases for switchIndex with EXPECTED_INDEX_COUNT
 * - Index lifecycle with refactored methods
 */

Sometimes a backward compatibility change spans two versions. A common case is a new functionality
that needs a BWC bridge in an unreleased versioned of a release branch (for example, 5.x).
To test the changes, you can instruct Gradle to build the BWC version from a another remote/branch combination instead of
pulling the release branch from GitHub. You do so using the `bwc.remote` and `bwc.refspec.BRANCH` system properties:

   * fewer than {@code k} have been offered, in the order specified by the factory used to create
   * this {@code TopKSelector}.
   *
   * <p>The returned list is an unmodifiable copy and will not be affected by further changes to
   * this {@code TopKSelector}. This method returns in O(k log k) time.
   */
  public List<T> topK() {
    @SuppressWarnings("nullness") // safe because we pass sort() a range that contains real Ts

import org.codelibs.fess.opensearch.user.exentity.User;

/**
 * Authentication chain implementation that executes external commands for user operations.
 * Provides user management through command-line tool execution for password changes and user deletion.
 */
public class CommandChain implements AuthenticationChain {

    private static final Logger logger = LogManager.getLogger(CommandChain.class);

    /** Working directory for command execution. */

        assertEquals(provider1, provider1); // Self equality
        assertFalse(provider1.equals(null)); // Null check
        assertFalse(provider1.equals("string")); // Type check
    }

    // Test with rapid config changes
    @Test
    public void test_rapidConfigChanges() {
        for (int i = 0; i < 50; i++) {
            final int adjustment = i * 1000;
            FessConfig rapidConfig = new FessConfig.SimpleImpl() {

// This should be always:
String value = getSomeProperty().get()
```

## Consequences

* We are incurring debt that will need to be paid later via deprecations or breaking changes to existing classes. The implementation for some Gradle types will be more complicated than an equivalent clean-sheet implementation.