techazard

In my quest to master Rust, I'm building a (toy) Soulseek client in Rust. Souleek is an old (2001) closed-source p2p network still used to share underground music.

For learning purposes, I'm imposing the following restrictions:

- I can't use external dependencies (crates)

- I have to reverse engineer the Soulseek protocol myself

So far it's been a lot of fun and rewarding as it touches upon low-level concepts I don't have to deal with normally as a web dev.

Yep you can create ambiguous nasty code like this. It's is clearly not expressing intent, so you would add parentheses.

It's actually nice that it does not matter if it's a function or attribute that your calling in ruby. Check out the Uniform access principle (https://en.wikipedia.org/wiki/Uniform_access_principle).

When used correctly you can write IMHO really clean and concise OOP code where (cascading) changes are easily made.