












next_peer_id is used only to iterate over peers? it causing that id bug


next_peer_id is used only to iterate over peers? it causing that id bug Peers itself should iterate over PeerMap from the start otherwise vacant ids will end after 15th connection from the same endpointself.next_peer_id = PeerId(0); after getting raw pointer made it work for menext_peer_id used for? (edited)




















next_peer_id used for? (edited)


thread 'main' panicked at 'Custom { kind: WouldBlock, error: "write would block" }', ...\event_loop\src\lib.rs:93:57self.net.tick(&mut self.socket).foreach(|e| panic!("{:?}", e));
in
fn run<A: Application<SocketLoop>>(mut self, mut application: A)
panic! to eprintln!
















1

























