This should significantly reduce the time it takes to join a server for the first time after it wipes. It may also reduce the number of players seeing "Rust is not responding" pop ups while joining servers for the first time. thumb_up534 ...
Names are not removed from the set when a user disconnects, so after a name is taken it can never be used again, not until we restart the server. Unfortunately there's a tricky obstacle we have to overcome before we can fix this....
Anyway, that was long detour. Let's get back to our chat server.11) Freeing user's name if they disconnectWe have a bug in our code. Names are not removed from the set when a user disconnects, so after a name is taken it can never be used again, not until we resta...
Names are not removed from the set when a user disconnects, so after a name is taken it can never be used again, not until we restart the server. Unfortunately there's a tricky obstacle we have to overcome before we can fix this....
Anyway, that was long detour. Let's get back to our chat server.11) Freeing user's name if they disconnectWe have a bug in our code. Names are not removed from the set when a user disconnects, so after a name is taken it can never be used again, not until we restart the ...
Anyway, that was long detour. Let's get back to our chat server.11) Freeing user's name if they disconnectWe have a bug in our code. Names are not removed from the set when a user disconnects, so after a name is taken it can never be used again, not until we restart ...
Users within a room are not discoverable. Let's add a /users command that will list the users in the current room. To do that we'll have to add a HashSet<String> to the Room struct and update many of the Rooms methods to also take a user name when joining, changing, o...
Users within a room are not discoverable. Let's add a /users command that will list the users in the current room. To do that we'll have to add a HashSet<String> to the Room struct and update many of the Rooms methods to also take a user name when joining, changing, or ...
Names are not removed from the set when a user disconnects, so after a name is taken it can never be used again, not until we restart the server. Unfortunately there's a tricky obstacle we have to overcome before we can fix this....
// consuming:: Emitted for locals that are being consumed when use in a function call. // controlFlow:: Emitted for control-flow related tokens, this includes the `?` operator. // crateRoot:: Emitted for crate names, like `serde` and `crate`. // declaration:: Emitted for names of ...