Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> It seems like with Rust it's not quite aware of which patterns to use, especially when the actual changes required may span multiple files due to the way memory management is structured.

What do you mean? Memory management is not related to files in Rust (or most languages).



When did they say that?


As far as I can tell, in the extract I quoted. Do you interpret it differently?


> It seems like with Rust it [the AI] is not quite aware of which patterns to use, especially when the actual changes required may span multiple files due to the way memory management is structured.

In rust, when you refactor something that deals with the borrow checker's shenanigans, you will likely have to change a bunch of files (from experience). This means that an AI will likely also have to change a bunch of files which they say the AI isn't so good at. They don't say this HAS to happen, just that it usually does because the borrow checker is an asshole.

This aligns with my experience as well, though I dealt with Rust before there was AI, so I can say little in regards to how the AI deals with that.


Thank you for the breakdown, this is exactly what I meant.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: