Alice Ryhl

So I've seen them sometimes say, we think this is a Lips API decision and we will go with whatever Lips API decides.

RFC, request for comment, is the way the Rust project makes big decisions.

But, you know, big ones is important to say.

Basically, the way it works is, let's say you have a language feature that's kind of big.

For example, I had one called DriveSmartPointer, which...

basically make some types in the standard library less special.

So, I mean, sometimes people begin implementation already, but the idea is that you write the RFC first.

You write this doc and it has a template.

And I think it's actually a pretty good template.

The idea is the first section is, I think, motivation.

Well, the first one is summary.

But the first important one is motivation.

We explain why this feature.

And then I think they have two really interesting sections.

They have the guide level explanation and the reference level explanation.

And what this is, is that in the guide level explanation, you explain your feature and

as if you were writing a guide, as if the feature already existed.

And in the reference level explanation, you explain your feature again as if it already existed, but as if it would be in the language reference instead of a tutorial.

Yeah, so, you know, you get to explain.

So rational and alternatives, I think, is a pretty important section because you get to answer all of the questions before they get asked.