News for hackers. Stuff that matters.
Re:Evergreen: A Provably Safe Systems Language by jordan_bonecut on Wednesday November 04, 2026 @10:25AM (#50366920)
This language has been something I've wanted to build for years. For a while I thought I'd get my PhD and build it there. But now it's very possible to have Claude build it while I'm at work and give it intense code review every day. It's still not in a "useful" place yet, but I'm curious what fellow programmers think of a language like this. If I continue work is this something anyone thinks they'd enjoy using? Would love some feedback, thanks!
Re:Evergreen: A Provably Safe Systems Language by sblom on Wednesday November 04, 2026 @10:53AM (#50367366)
It's a really great concept. What guarantees are made by the prover?

Success in programming languages is not simply if-you-build-it-they-will-come. Bootstrapping a community that loves programming in it is the hard part. You'll either need a killer interop story with an already built ecosystem, or you'll need your own HTTP server, JSON parser, etc. etc. etc.

Best of luck! I'll watch this space.

Re:Evergreen: A Provably Safe Systems Language by jordan_bonecut on Wednesday November 04, 2026 @10:57AM (#50367444)
Thanks! The guarantee is that, without the use of trustme (which can prove any fact), you cannot address memory as the wrong type. The compiler also ensures that a pointer/reference to a value is live at compile time, so it’s not possible to create an invalid pointer (without the use of trustme). You can also claim any fact which the compiler must prove in order to continue compilation.

That is good advice, I’m definitely planning on including some batteries soon, once I’m very happy with where the compiler is at.

Re:Evergreen: A Provably Safe Systems Language by yunnpp on Wednesday November 04, 2026 @09:22PM (#50374308)
> You'll either need a killer interop story with an already built ecosystem

On that note: allow me to "import" or "use" a C header without writing any FFI code.

Re:Evergreen: A Provably Safe Systems Language by 0c3ca83 on Wednesday November 04, 2026 @11:58AM (#50368400)
It's so strange how much effort goes into producing a language that you don't even care enough about the write.
Re:Evergreen: A Provably Safe Systems Language by gchamonlive on Wednesday November 04, 2026 @12:05PM (#50368490)
[delayed]
Re:Evergreen: A Provably Safe Systems Language by 0c3ca83 on Wednesday November 04, 2026 @12:20PM (#50368661)
you can ask ai to write code in existing languages with large training sets, and it'll do better because of the large volume of training data.

if you're all-in on ai, you want to prioritize familiarity for agents.

Re:Evergreen: A Provably Safe Systems Language by gchamonlive on Wednesday November 04, 2026 @12:24PM (#50368693)
[delayed]
Re:Evergreen: A Provably Safe Systems Language by ModernMech on Wednesday November 04, 2026 @01:14PM (#50369389)
That would imply the AI should write every program in Python from now until the end of time; but just because the AI is most familiar with Python doesn’t mean we have to throw everything we know about system design and using the right tools for the job out of the window.
Re:Evergreen: A Provably Safe Systems Language by 0c3ca83 on Wednesday November 04, 2026 @02:55PM (#50370657)
Yes, Python or Rust would make sense.
Re:Evergreen: A Provably Safe Systems Language by ModernMech on Wednesday November 04, 2026 @03:57PM (#50371402)
Not in every situation for all time, that's my point. Which language the AI should use will evolve over time as use cases and computing hardware evolve. It isn't the case that language design is now ossified at whatever existed in 2023.

Also, what you're saying implies Python and Rust should stop evolving as languages, as changing the language would invalidate the vast quantity of work the AI has been trained on.

Re:Evergreen: A Provably Safe Systems Language by 0c3ca83 on Wednesday November 04, 2026 @04:19PM (#50371695)
> Not in every situation for all time, that's my point.

I think I mostly disagree.

Re:Evergreen: A Provably Safe Systems Language by gchamonlive on Friday November 06, 2026 @12:51PM (#50395731)
[delayed]
Re:Evergreen: A Provably Safe Systems Language by jeremyloy_wt on Wednesday November 04, 2026 @12:06PM (#50368497)
To me it’s about determinism and feedback. Agents will make mistakes but if they get clear feedback from the tools they use, they will produce a good result.

There are a shrinking number of reasons to geenfield projects with non-strict or unsafe languages now.

Re:Evergreen: A Provably Safe Systems Language by empath75 on Wednesday November 04, 2026 @12:41PM (#50368947)
This isn't so much directed at you, as other people that get inspired by this. I have been working on my own Rust like language with claude for a few months and there are a _lot_ of projects like that out there.

Mine has a formally proven borrow checker built on linear types, along with algebraic effects, with an LLVM compiler written in lean -- the type checker uses exactly the proven calculus.

If you are going to build a language with claude, I highly, highly recommend writing it in Lean or Coq and starting by formalizing a pre-existing paper or system that has the properties you want.

Claude gets confused and takes shortcuts constantly, and if you don't have a proven base, you are really going ot struggle.

Re:Evergreen: A Provably Safe Systems Language by amccollum on Wednesday November 04, 2026 @01:42PM (#50369771)
Is your language available anywhere? I'd be curious to check it out. I strongly believe that there will eventually be a new language created with agents in mind as the primary consumers, and making the foundations provable / safe are key cornerstones in my mind. The other property that I think is very important is fast tooling / compilation. Compilation speed is not generally the bottleneck right now in agent loops, but models can get faster, and as software scales up and is written by swarms of agents in concert, making the tools run really fast will be an important way to decrease cycle time and increase speed.
Re:Evergreen: A Provably Safe Systems Language by empath75 on Wednesday November 04, 2026 @02:06PM (#50370092)
> I strongly believe that there will eventually be a new language created with agents in mind as the primary consumers

That is exactly my motivation. The purpose of adding effects to my language, for example, was at least partially so you can track changes to things like IO usage in PRs. I also plan on adding a simple proof DSL that surfaces some lean functionality directly into the surface, so you can prove invariants about code as in this language, or surface exactly what is being trusted when writing the equivalent of unsafe code.

The main thing I am trying to solve is the LLM code review problem, really.

Re:Evergreen: A Provably Safe Systems Language by norman784 on Thursday November 05, 2026 @03:11AM (#50376507)
I was thinking about this problem and found a while ago that Unison lang has a cool concept, I recommend you give it a read [0].

- [0] https://www.unison-lang.org/docs/the-big-idea/

Re:Evergreen: A Provably Safe Systems Language by ChickeNES on Wednesday November 04, 2026 @02:05PM (#50370074)
Why optimize for old fashioned manual programming, especially since you are vibe coding the language to begin with? Unless you think Claude and friends will “enjoy” using it more.
Re:Evergreen: A Provably Safe Systems Language by jordan_bonecut on Wednesday November 04, 2026 @03:57PM (#50371405)
Because good tools are good
Re:Evergreen: A Provably Safe Systems Language by n_u on Wednesday November 04, 2026 @04:16PM (#50371650)
This is cool! Thanks for sharing. I've been wanting something like this for a while

1. I'm curious how this handles I/O? Proving stuff is often really useful for distributed systems where we would like to prove our system behaves correctly under any ordering of I/O operations.

2. How does this compare to just using Rust and some proof tool like Kani or Verus?