BitSet must document its thread-safety

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P4
    • 1.4.0
    • Affects Version/s: 1.3.0
    • Component/s: core-libs
    • None
    • beta2
    • generic
    • generic
    • Verified

        BitSet performs no synchronization. Its specification should make this clear. Currently, it is misleading: the spec for the hashCode method vaguely implies that it is thread-safe. The misleading occurrence of the synchronized keyword should be removed, and a note should be added to the class comment explaining that the class requires external synchronization if it is to be used in a multithreaded setting.

            Assignee:
            Michael Mccloskey (Inactive)
            Reporter:
            Josh Bloch (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: