Chris Lattner

It's been implemented in Swift and Rust and many languages.

So it's not Haskell, which is where everybody learns their tricks from.

But we need to implement that and that'll enable a new level of expressivity.

So classes.

Well, and so this comes back to the where Mojo came from and the fact that this is 0.1, right?

And so we're building, so modular is building an AI stack, right?

And an AI stack has a bunch of problems working with hardware and writing high-performance kernels and doing this kernel fusion thing I was talking about and getting the most out of the hardware, right?

And so we've really prioritized and built Mojo to solve Mojo's problem.

Right now, our North Star is build out and support all the things.

And so we're making incredible progress.

By the way, Mojo is only like seven months old.

So that's another interesting thing.

Yeah.

And so, I mean, but also you look into, it's, it's amazing how much is also there and you take it for granted that a value, if you define it, it will get destroyed automatically.

Like that little feature itself is actually really complicated, given the way the ownership system has to work.

And the way that works within Mojo is a huge step forward from what Rust and Swift have done.

But can you say that again?

When a value, when you define it, it gets destroyed automatically.

Yeah, so like say you have a string, right?

So you just find a string on the stack, okay?