3 ms·
> No, is HOW Rust use type signatures. No, I don't really agree. The example was "def read(path)", which is intentionally vague and any typed language would cl
by void_mint 5y ago
> No, is HOW Rust use type signatures.
No, I don't really agree. The example was "def read(path)", which is intentionally vague and any typed language would clarify.
Your points can be/are valid, but they don't really change the fact that the above example was a cherry pick, and Rust's (over)use of symbols and special characters make it, again, about as hard to read as one could imagine. Just because you _can_ derive meaning from it doesn't change that.
- mamcx 5y agoOk, so how you do it or what can be used as counter-example?
- void_mint 5y agofunc Read (p Path) ([]byte, error) From your post: > What is path? Anything that can become path on the file system. > What it read? Anything that can be pointed with that PATH > What it return? Vec of bytes or a IO::Error