refactor(bitswap/message) use map to prevent duplicate entries
Brian Tiger Chow authored
A nice invariant for bitswap sessions:

        Senders and receivers can trust that messages do not contain
        duplicate blocks or duplicate keys. Backing the message with a
        map enforces this invariant.

        This comes at the cost of O(n) getters.
f94d6a37
Name Last commit Last update
..
bitswap
offline
interface.go