3 ms·
My experience learning and using Rust over the last 9 months has included a lot of repeats of this: 1. Write some code that does something tricky with borrowed
by mleonhard 6y ago
My experience learning and using Rust over the last 9 months has included a lot of repeats of this:
1. Write some code that does something tricky with borrowed types
2. It won't compile. Search online for the error message. Find the Rust github issue about adding support for doing things that way.
3. Try to find or think up a different way to write the code. Go to 1.
GP is referring to changes that make compilation succeed at step 1. These changes will save newbs from many hours of frustration. The cost of these changes is minimal. Actually they free up a lot of mental capacity currently used for workarounds.
I'm really happy with Rust and the steady progress made by the core team. Rust stable is really excellent to work with.
- foerbert 6y agoI understand that. And I still think these changes might be particularly expensive ones. Trying to keep track of what workarounds you do and do not need to use is hard. Removing workarounds is good, but still an expensive step. Applying a large set of rules can be quite easy after an adaptation period, but changing those rules remains hard. Even if the new rules are simpler. I'm not saying Rust shouldn't be making these changes. I'm just saying I think this might be part of the reason why you hear comments about how hard it is to keep up with Rust.