Writing fast code under optimizing compilers feels similar to *prompting: 1) Developing an intuitive understanding of how the model combines your patterns to outputs 2) Knowing what a "good" output is, in regards to correction.
* any deterministic ML inference with text input
Today, we’re announcing the preview release of ty, an extremely fast type checker and language server for Python, written in Rust.
In early testing, it's 10x, 50x, even 100x faster than existing type checkers. (We've seen >600x speed-ups over Mypy in some real-world projects.)
@charliermarsh The new rustc-hash algorithm is actually different than foldhash. rustc-hash is optimized specifically for the compiler's usage, while foldhash is more general purpose.
@mitsuhiko Would it feel different if zerocopy was an official rust-lang repository backed by a working group? I think that's essentially the idea here.
@GustavSterbrant @olson_dan If this level of safety is not important to you then Rust might not be for you, but once you appreciate it the experience becomes a lot more enjoyable. And to be honest there's only a handful of patterns you have to come to understand before feeling relatively comfortable.
@GustavSterbrant @olson_dan That's fair, but Rust's goal is to force you to think more about what exactly you're doing. Another language would let you trivially create globally mutable state, which you can also do in Rust, it just makes it less accessible because that's probably not what you actually want.