3 ms·
Not really. Even humans regularly get lifetimes wrong. As someone not super experienced in Rust, my workflow was often very very compiler-error-driven. I would
by cardanome 1y ago
Not really. Even humans regularly get lifetimes wrong.
As someone not super experienced in Rust, my workflow was often very very compiler-error-driven. I would type a bit, see what it says, changes it and so on. Maybe someone more experienced can write whole chucks single-pass that compile on first try but that should far exceed anything generative AI will be able to do in the next few years.
The problem here is that iteration with AI is slow and expensive at the moment.
If anything you want to use a language with automatic garbage collection as it removes mental overhead for both generative AI as well as humans. Also you want to to have a more boilerplate heavy language because they are more easily to reason about while the boilerplate doesn't matter when the AI does the work.
I haven't tried it but I suspect golang should work very well. The language is very stable so older training data still works fine. Projects are very uniform, there isn't much variation in coding style, so easy to grok for AI.
Also probably Java but I suspect it might get confused with the different versions and all the magic certain frameworks use.
- greenavocado 1y agoAll LLMs still massively struggle with resource lifetimes irrespective of the language
- hu3 1y agoIMO they struggle a whole lot more with low level/manual lifetimes like C, C++ and Rust.