3 ms·
I got the idea by following the Rust tutorials and then making 'simple' programs, seeing the errors, going to Rust resources and getting the advice 'just cut an
by jhayward 6y ago
I got the idea by following the Rust tutorials and then making 'simple' programs, seeing the errors, going to Rust resources and getting the advice 'just cut and paste the expected type'. The expected types generally had 6-8 ':'s, and three to four deep nested type specifiers.
- Rusky 6y agoIf a significant part of those types was just something like `std::collections::` or similar then I'm not sure I see the problem. Suggestions should probably trim redundant prefixes like that, but recognizing standard library namespaces shouldn't be a big obstacle to understanding either.
- jhayward 6y agoI haven't been back to rust since, so I don't have the specifics. But it was clear to me that this was not a helpful way to program. It was also crystal clear that, like C++, Rust puts many barriers to true abstraction. You have to know many, many details of how a specific type is implemented, sometimes several levels deep, to correctly use it at a high level. The cognitive overhead is enormous.
- Rusky 6y agoIn Rust's target domain(s), those details often turn out to be quite relevant. Hiding them basically amounts to targeting a different domain. This is very different from being irrelevant and noisy.