Alice Ryhl

If you have, I don't know, a pull request changing something in the reference, then the language team might say, oh, we need to make sure that everybody is on board with this change.

They'll tell the bot to start an FCP on this random PR or some random issue or wherever it might be.

The same process applies.

But you put the feature behind a feature flag.

In Rust, we have this thing called nightly features, which basically means that you can't use it normally.

But if you use the nightly build of the compiler, you can.

Once you have your feature, I mean, you might begin.

But, you know, once you have your accepted RFC, you start submitting pull requests, you implement your feature, it gets merged, and people start using it experimentally.

Yeah, and then at some point, you might say, okay, I think this feature is ready.

And this is kind of a recent invention, but we have come up with this idea of a stabilization report.

In the pull request that removes the feature flag, we write up a little report saying,

For example, how it's been used and explaining like, oh, here are the dangerous edge cases.

Here are the tests for each of the dangerous edges.

So that kind of stuff.

And then they use the FTP process again to agree to stabilize it.

And then it's merged.

And so now you have a feature without a feature flag.

In the main branch.

Between zero days and six weeks from that, there will be a beta release of the compiler, and it will be... And it will be in it.

Yeah, it will be in it.