Chris Lattner

Same thing as the Swift team, right?

And this is where one of the reasons we released Mojo much earlier is so we can get feedback.

And we've already renamed a keyword due to community feedback.

Which one?

uh we use an ampersand and now it's named in out we're not we're not renaming existing python keywords because that breaks compatibility right we're naming things we're adding and making sure that they are designed well we get usage experience we iterate and work with the community because again if you scale something really fast and everybody writes all their code and they start using it in production then it's impossible to change and so you want to learn from people you want to iterate and work on that early on and this is where design discussions it's it's actually quite important

You should totally file a feature request.

People have told me that I'm insane.

I'm liking this.

I mean, it's funny.

You come back to the flame emoji file extension, right?

We have the option to use the flame emoji, which just even that concept caused, for example, the people at GitHub to say, now I've seen everything.

I think the world is ready for this stuff, right?

And so when we have a package manager, we'll clearly have to innovate by having the compiled package thing be the little box with the bow on it, right?

I mean, it has to be done.

I mean, as a today snapshot, which will be obsolete tomorrow, the lifetime stuff is really exciting.

And so lifetimes give you safe references to memory without dangling pointers.

And so this has been done in languages like Rust before.

And so we have a new approach, which is really cool.

I'm very excited about that.

That'll be out to the community very soon.