On Mon, Oct 10, 2022 at 5:05 PM David Gebler <davidgeb...@gmail.com> wrote:
> On Tue, Oct 11, 2022 at 12:05 AM David Rodrigues <david.pro...@gmail.com> > wrote: > > > The idea is that the experimental features are exclusively something that > > the PHP team has voted for (approved) and that will be part of the > language. > > > > So they're not experimental features, they're accepted RFCs, maybe with a > lower voting threshold. > > I don't really see what the confusion is about. It's for features that we have all agreed to include, but that the public API or behavior might change in minor versions while usage information, feedback, and so-on happens. The idea behind an experimental inclusion would be something like "the concept behind this feature we've agreed to include, unless something truly drastic comes up once it's out in the wild, but the syntax, parameters, and signatures might change while we look at usage and real-world code. It's like the opposite of a Deprecation notice in my mind... it's a flag on specific code that lets people know *ahead of time* that BC breaks in a minor version might be necessary for this feature for a little while. Jordan
