| ▲ | n_u 9 hours ago | ||||||||||||||||||||||
This is my second attempt learning Rust and I have found that LLMs are a game-changer. They are really good at proposing ways to deal with borrow-checker problems that are very difficult to diagnose as a Rust beginner. In particular, an error on one line may force you to change a large part of your code. As a beginner this can be intimidating ("do I really need to change everything that uses this struct to use a borrow instead of ownership? will that cause errors elsewhere?") and I found that induced analysis paralysis in me. Talking to an LLM about my options gave me the confidence to do a big change. | |||||||||||||||||||||||
| ▲ | augusteo 9 hours ago | parent | next [-] | ||||||||||||||||||||||
n_u's point about LLMs as mentors for Rust's borrow checker matches my experience. The error messages are famously helpful, but sometimes you need someone to explain the why. I've noticed the same pattern learning other things. Having an on-demand tutor that can see your exact code changes the learning curve. You still have to do the work, but you get unstuck faster. | |||||||||||||||||||||||
| ▲ | pfdietz 9 hours ago | parent | prev | next [-] | ||||||||||||||||||||||
I don't see why it shouldn't be even more automated than that, with LLM ideas tested automatically by differential testing of components against the previous implementation. EDIT: typo fixed, thx | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | monero-xmr 9 hours ago | parent | prev [-] | ||||||||||||||||||||||
I am old but C is similarly improved by LLM. Build system, boilerplate, syscalls, potential memory leaks. It will be OK when the Linux graybeards die because new people can come up to speed much more quickly | |||||||||||||||||||||||
| |||||||||||||||||||||||