Use `::bind_any()` instead of `::bind(addr)` in example for client to avoid confusion

[DragonAxe]

In the server_client.rs example, there are two address:port constants, one for the server and one for the client:

laminar/examples/server_client.rs

Line 10 in db4873c

const SERVER: &str = "127.0.0.1:12351";

laminar/examples/server_client.rs

Line 51 in db4873c

let addr = "127.0.0.1:12352";

These addresses are 40 lines apart, so I missed that the port numbers are different. Port 12351 for the server and 12352 for client. When adapting the example to my project, I accidentally merged the two addresses to one variable.

I feel it would be better to use ::bind_any() instead of ::bind(addr) for the client to help prevent the confusion I encountered.

laminar/examples/server_client.rs

Line 52 in db4873c

let mut socket = Socket::bind(addr)?;

It seems common for client programs to pick any open port to bind to which is why ::bind_any() seems like a good option.

[merlinaudio]

I learned about bind_any through your post. Thank you!