* that gets messy here, and we already have null tests for Range.
   */

  /*
   * These generators also rely on consecutive integer inputs (not necessarily in order, but no
   * holes).
   */

  // SetCreationTester has some tests that pass in duplicates. Dedup them.

### Core Design Principles
CoreLib follows a **utility-class pattern** where most functionality is exposed through static methods:

- **Assertion-based validation** - All methods validate inputs using `AssertionUtil.assertArgumentNotNull()` and `AssertionUtil.assertArgumentNotEmpty()`

        verify(cache, never()).resolveSids0(any(), any(), any());
    }

    @Test
    @DisplayName("resolveSids(CIFSContext,server,sids,offset,length) throws on invalid inputs")
    void resolveSids_invalidInputs() throws Exception {
        SIDCacheImpl cache = new SIDCacheImpl(mock(CIFSContext.class));
        CIFSContext ctx = mock(CIFSContext.class);

        // Null sids array -> NPE

  /**
   * Returns a {@code Collector} that accumulates elements into an {@code ImmutableSortedMultiset}
   * whose elements are the result of applying {@code elementFunction} to the inputs, with counts
   * equal to the result of applying {@code countFunction} to the inputs.
   *
   * <p>If the mapped elements contain duplicates (according to {@code comparator}), the first

labels.webApiJson=JSON Response
labels.webConfigName=Web Crawl Config Name
labels.allLanguages=All Languages
labels.dictId=Dictionary ID
labels.docId=Document ID
labels.endTime=End Time
labels.hq=hq
labels.inputs=Inputs
labels.jobLogging=Logging
labels.jobName=Name
labels.jobStatus=Status
labels.labelTypeIds=Labels
labels.lang=Language
labels.outputs=Outputs
labels.pos=Part-of-speech

 * advantage of that for convertAll, as discussed on that method.)
 *
 * 2. The supertype of this class could be `Function<@Nullable A, @Nullable B>`, since
 * Converter.apply (like Converter.convert) is capable of accepting null inputs. However, a
 * supertype of `Function<A, B>` turns out to be massively more useful to callers in practice: They
 * want their output to be non-null in operations like `stream.map(myConverter)`, and we can

        assertEquals(expectedLong, LongMath.binomial(n, k));
      }
    }
  }


  @GwtIncompatible // Slow
  public void testBinomial_exhaustiveNotOverflowing() {
    // Tests all of the inputs to LongMath.binomial that won't cause it to overflow, that weren't
    // tested in the previous method, for k >= 3.
    for (int k = 3; k < LongMath.biggestBinomials.length; k++) {

   * that gets messy here, and we already have null tests for Range.
   */

  /*
   * These generators also rely on consecutive integer inputs (not necessarily in order, but no
   * holes).
   */

  // SetCreationTester has some tests that pass in duplicates. Dedup them.

        CIFSException ex = assertThrows(CIFSException.class, () -> ctx.verifyMIC(data, mic));
        assertTrue(ex.getMessage().contains("Failed to verify MIC"));
    }

    @Test
    @DisplayName("verifyMIC with null inputs throws NPE")
    void verifyMIC_nullInputs() {
        assertThrows(NullPointerException.class, () -> ctx.verifyMIC(null, new byte[] { 1 }));

	// LDADDx/SWPx/CASx atomic instructions
	return arm64.IsAtomicInstruction(op)
}

// IsARM64TBL reports whether the op (as defined by an arm64.A*
// constant) is one of the TBL-like instructions and one of its
// inputs does not fit into prog.Reg, so require special handling.
func IsARM64TBL(op obj.As) bool {
	switch op {
	case arm64.AVTBL, arm64.AVTBX, arm64.AVMOVQ:
		return true
	}
	return false
}