4 ms·
Was the paper really written 2 years ago? The paper states "We exclude error codes that are no longer relevant in the latest version of the Rust compiler (1.67
by croemer 1y ago
Was the paper really written 2 years ago?
The paper states "We exclude error codes that are no longer relevant in the latest version of the Rust compiler (1.67.1)".
A quick search shows that Rust 1.68.0 was released in March 2023: https://releases.rs/docs/1.68.0/ https://releases.rs/docs/1.68.0/
Update: looks like it really is 2 years old. "We evaluate both GPT-3.5-turbo (which we call as GPT-3.5) and GPT-4"
- meltyness 1y agoYeah, the problem LLMs will have with Rust is the adherence to the type system, and the type system's capability to perform type inference. It essentially demands coherent processing memory, similar to the issues LLMs have performing arithmetic while working with limited total features. https://leetcode.com/problems/zigzag-grid-traversal-with-skip/solutions/6537775/pure-fp-functional-solution-by-meltyness-z7zc/ https://leetcode.com/problems/zigzag-grid-traversal-with-ski... Here's an example of an ostensibly simple problem that I've solved (pretty much adversarially) with a type like: StepBy< Cloned< FlatMap< Chunks<Vec<i32>>, FnMut<&[i32]> -> Chain<Iter<i32>, Rev<Iter<i32>> > > > > So this (pretty much) maximally dips into the type system to solve the problem, and as a result any comprehension the LLM must develop mechanistically about the type system is redundant. It's a pretty wicked problem the degree to which the type system is used to solve problems, and the degree to which imperative code solves problems that, except for hopes and wishes, which portions map from purpose to execution will likely remain incomprehensible.