import org.jspecify.annotations.Nullable;

/**
 * An extension of {@code DataInput} for reading from in-memory byte arrays; its methods offer
 * identical functionality but do not throw {@link IOException}.
 *
 * <p><b>Warning:</b> The caller is responsible for not attempting to read past the end of the
 * array. If any method encounters the end of the array prematurely, it throws {@link

        // Then
        assertEquals(expectedLength, actualLength);
        verify(messageBlock).encode(dst, dstIndex);
    }

    @Test
    @DisplayName("Test setDigest and getDigest methods")
    void testSetAndGetDigest() {
        // Given
        doNothing().when(messageBlock).setDigest(digest);
        when(messageBlock.getDigest()).thenReturn(digest);

        // When

 *
 * <p>The methods returning collections or maps always return views of the underlying table.
 * Updating the table can change the contents of those collections, and updating the collections
 * will change the table.
 *
 * <p>All methods that modify the table are optional, and the views returned by the table may or may
 * not be modifiable. When modification isn't supported, those methods will throw an {@link

    public synchronized void mark(final int readlimit) {
        inputStream.mark(readlimit);
    }

    /**
     * Tests if this input stream supports the mark and reset methods.
     *
     * @return true if this stream instance supports the mark and reset methods; false otherwise
     */
    @Override
    public boolean markSupported() {
        return inputStream.markSupported();
    }

    /**

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

/**
 * @deprecated Use MavenStaxWriter instead
 */
@Deprecated
public class MavenXpp3WriterEx extends MavenXpp3Writer {

    // -----------/
    // - Methods -/
    // -----------/

    public MavenXpp3WriterEx() {
        super(true);
    }

    /**
     * Method setFileComment.
     *
     * @param fileComment a fileComment object.
     */
    @Override
    public void setFileComment(String fileComment) {

        assertNotSame(response1, response2);
        assertEquals(100, response1.getAvailable());
        assertEquals(0, response2.getAvailable());
    }

    @Test
    @DisplayName("All write methods should consistently return 0")
    void testAllWriteMethodsReturnZero() {
        // Arrange
        byte[] buffer = new byte[100];

        // Act & Assert

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code