refactor(bitswap/message) use map to prevent duplicate entries
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.
Showing
Please register or sign in to comment