Around https://github.com/libp2p/go-libp2p-kbucket/blob/master/table.go#L61.
RoutingTable updates don't evict any entries; and the evicted return value remains initialized.

or even unfoldWildcardBucket

Empty buckets, especially at the end of the routing table, can cause really tricky issues. We should try to collapse them when possible.

@guillaumemichel just pushed a release tag: v0.6.0.
Please manually verify validity (using `gorelease`), and update `version.json` to reflect the manually released version, if necessary.
In the future, please use the automated process.

Based on some good ideas by @aschmahmann , here's a couple of things we can do to improve how we manage the replacement cache & "dead" peers:

1. Since the replacement cache is bounded, we could lose potential candidates if it's full. So, when we eject a candidate from the replacement cache either because it goes into the RT or it's not reachable, we should replace it with a connected peer that is neither in the RT nor in the replacement cache.
   See libp2p/go-libp2p-kad-dht#482 (comment) for the motivating discussion.

2. When DHT calls HandleDeadPeer on the RT for a peer, we immediately eject it from the RT without replacing it. Currently, the DHT does this for a connected peer that stops being a DHT server. We should replace such peers.

Hi, when I try to run go get github.com/libp2p/go-libp2p-kbucket I get the following message:

../../libp2p/go-libp2p-kbucket/peerdiversity/filter.go:13:2: no Go files in ~/go/src/github.com/libp2p/go-libp2p-asn-util`

Any idea what is causing this and how to fix it?

We've begun to pass in some constructor arguments as nil if we don't need them. It's time to introduce functional options to the Routing Table.

We need to move the code that listens for various events (PeerProtocolUpdated, PeerDisconnected/Connected etc etc) into a single event loop inside the Routing Table.

There's no reason to keep it in the DHT since we eventually want the RT to be a self sustaining data structure. This will also help prevent race conditions that arise in managing the RT/replacement-cache & make the code easy to reason about.

Once libp2p/go-libp2p#801 goes in, we only need to depend on the event bus for all the relevant events & so will not have to depend on the host.

The comment for ListPeers in table.go has

// NOTE: This is potentially unsafe... use at your own risk

Why is ListPeers potentially unsafe?