[zozbot234]

> undefined behavior that even a mid-level C++ dev could have easily caught (assuming iterator stability in a vector that was being modified)

This is not an AI thing, plenty of "mid-level" C++ developers could have made that same mistake. New code should not be written in C++.

(I do wonder how Claude AI does when coding Rust, where at least you can be pretty sure that your code will work once it compiles successfully. Or Safe C++, if that ever becomes a thing.)

[sampullman]

It does alright with Rust, but you can't assume it works as intended if it compiles successfully. The issue with current AI when solving complex or large scale coding problems is usually not syntax, it's logical issues and poor abstraction. Rust is great, but the borrow checker doesn't protect you from that.

I'm able to use AI for Rust code a lot more now than 6 months ago, but it's still common to have it spit out something decent looking, but not quite there. Sometimes re-prompting fixes all the issues, but it's pretty frustrating when it doesn't.

[zozbot234]

That's why I said "work" (i.e. probably will do something and won't crash) not "work as intended". Big difference there!

[bugglebeetle]

I haven’t tried with the most recent Claude models, but for the last iteration, Gemini was far better at Rust and what I still use to write anything in it. As an experiment, I even fed it a whole ebook on Rust design patterns and a small script (500 lines) and it was able to refactor to use the correct ones, with some minor back and forth to fix build errors!

[steveklabnik]

I use Claude Code with Rust regularly and am very happy with it.

[jeffreygoesto]

Go ahead and modify A Python dict while iterating over it then.