-
Notifications
You must be signed in to change notification settings - Fork 577
[doc] Clarify the situation around smartmatch in perlexperiment #23272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can you point to the specific commits in which the disabling was implemented? (I ask because there were so many smartmatch-related issues that I lost track of where things stand.) Thanks. |
When I go to #22766, I see that it was closed with 0 commits and 0 files changed. I don't understand that -- so I'll take a pass on writing a p.r. to satisfy this ticket. :( |
I seems there was some kerfluffle around merging the PR. 15cbd20 is the commit that merged the |
I looked at this and wondered how to describe it's status. I don't think it's a current experiment, we're not planning on iterating on it's design for the same reason it wasn't removed. I don't think it's "so wildly successful and played so well with others" that it belongs in Accepted features. And it's no longer removed. Add a new section "Developmental Backwaters" or "Features we tried to remove"? |
Or "Failed Experiments that Stuck"? |
Or perhaps "Discouraged", since placing it behind a feature guard is implicitly saying that something is not suitable for widespread use? |
Missed the last "t" the first time I read that |
Where
pod/perlexperiment.pod
Description
The current document says about smartmatch:
Since that was written, the
smartmatch
feature was created, and smartmatch was not removed, but disabled in the:5.42
feature bundle.The text was updated successfully, but these errors were encountered: