2026 is an exciting year for the Rust compiler (and me)

(yoyo-code.com)

62 points | by panstromek 3 hours ago

7 comments

  • throwup238 30 minutes ago
    > It's easy to understate how big of a deal this is for the compiler. This work resolves a major piece of technical debt that a lot of compiler developers dreamed about for years.

    No kidding. I’ve been waiting for the solver at least half that decade now. Hopefully it and Polonius unblock specialization which has been in purgatory for years.

  • yhjc2692 1 hour ago
    Smaller target directory size would be such a lifesaver. Hoping the best for you, and Rust!
    • thomashabets2 1 hour ago
      It would help, yes. Here's one of my projects, that uses different subdirectories in target/ based on compiler options pre-commit runs:

          $ du -hcs target/
          190G    target/
  • hmokiguess 1 hour ago
    Pretty wild to see how different people’s experiences can be within the same industry but under different applications and circumstances, here is someone joyful about the future of a language whereas not long ago we had a Ruby gem maintainer in deep dissatisfaction and frustration with the future of it.

    Not implying to compare Rust and Ruby, just mainly observing how these two things came out near each other in the present day.

  • panstromek 2 hours ago
    I don't understandy why, but all submissions of this post so far had incorrect title. When I posted the correct one, it still got reassigned the wrong title and I had to edit it (and it didn't allow me to do that yesterday, only today).
    • tialaramex 1 hour ago
      Hacker News has some automatic fixes for title text. Some - perhaps all - of them can walk into false positives where a change that's usually desirable instead ruins the title either because it's a joke and the change spoils the joke or just because English is complicated.
  • jdbloodstone 47 minutes ago
    [flagged]
  • lolakutty 8 minutes ago
    Rust is not very relevant anymore when you can write it in C and once in a while run an LLM over it to catch any memory issues...