Java Collections API Design FAQ

Microsystems, S. (1998). Java Collections API Design FAQ.

Type

Unclassified

Intellectual base

Unclassified

Year

1998

Link

no authoritative link yet

Cited by

1 citation across 1 artifact.

Domain-specific

• Refused Bequest
  • The JDK adopted this design as a pragmatic compromise (avoiding a separate mutable/immutable type split throughout the collections framework)

    SupportedVerified against the source

    Read by an automated reader; not a human review. How support was checked

Verification

Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.

Does it back the claim? Read against the text for 1 of 1 citation: 1 supported. Each verdict is shown under its citation below, with what in the work backs the sentence.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Registry ID ref:7d12f8766113 · see in the full table