Chris Lattner

It's fine.

But in Mojo, if you declare a type and you use it, then it means it is going to be that type.

And the compiler helps you check that and force it.

And it's safe.

And it's not, it's not a like best effort hint kind of a thing.

Yeah, so Mojo is pretty hardcore in terms of what it tries to do in the language, which is the philosophy there is that we...

Again, if you look at Python, right?

Python's a beautiful language because it's so extensible, right?

And so all of the different things in Python, like for loops and plus, and like all these things can be accessed through these underbar, unbar methods, okay?

So you have to say, okay, if I make something that is super fast, I can go all the way down to the metal.

Why do I need to have integers built into the language?

And so what Mojo does is it says, okay, well, we can have this notion of structs.

So you have classes in Python.

Now you can have structs.

Classes are dynamic.

Structs are static.

Cool.

We can get high performance.

We can write C++ kind of code with structs if you want.

These things mix and work beautifully together.