Skip to content

feature: switch no longer being removed #23288

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

Open
wants to merge 1 commit into
base: blead
Choose a base branch
from

Conversation

tonycoz
Copy link
Contributor

@tonycoz tonycoz commented May 15, 2025

It no longer produces experimental warnings.

Fixes #23282


  • This set of changes does not require a perldelta entry.

It no longer produces experimental warnings.

Fixes Perl#23282
@Grinnz
Copy link
Contributor

Grinnz commented May 15, 2025

Is it also no longer deprecated?

@book
Copy link
Contributor

book commented May 15, 2025

Is it also no longer deprecated?

Indeed: the warning seems to have been removed in 2dd81b7.

The deprecated::smartmatch warning was added in v5.38, when we wanted to remove smartmatch entirely. I personally think that smartmatch should remain deprecated, even if we only remove it from the feature bundle, and not from the language.

@haarg, @ap, what are your thoughts on this?

@Grinnz
Copy link
Contributor

Grinnz commented May 15, 2025

It can always be re-deprecated if removal is again attempted, but at the very least, the documentation should indicate that it is discouraged and will receive no further development.

@tonycoz
Copy link
Contributor Author

tonycoz commented May 15, 2025

pod/perldeprecation.pod implies to me that if we deprecate something, we are going to remove it.

I doubt(ed) we'll be removing these features, so I removed the deprecations. And it was applied as is.

It might be worth reinstating the deprecation message and re-wording it to indicate discouragement instead of deprecation.

There's still some references to these being experimental, I'm not sure if those need re-wording, or we considered it the remnants of a failed experiment (the apparatus exploded, leaving a mess all over the lab.)

@guest20
Copy link

guest20 commented May 15, 2025

I'd like to suggest a kind of hypothetical feature::CoreList, that lets software tools programatically query a feature's experimental / available / deprecated / re-precated‡ status.

__
‡. undeprecated? dedeprecated? just precated?

@book
Copy link
Contributor

book commented May 15, 2025

We discussed the topic during the PSC meeting today, and concluded:

It’s not deprecated any more and it’s not experimental either. It’s just a negative feature. It’s a mistake we made that is now part of older language versions but will not be part of future feature bundles.

@book
Copy link
Contributor

book commented May 15, 2025

Also, I confused the switch feature and the smartmatch feature in my earlier comments.

@book
Copy link
Contributor

book commented May 15, 2025

I'd like to suggest a kind of hypothetical feature::CoreList, that lets software tools programatically query a feature's experimental / available / deprecated / re-precated‡ status.

The information is already available in Perl::Version::Bumper. It might be interesting to come up with a proper interface to access that data (it's only used internally by the module so far.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[doc] 'switch' feature still documented as removed in 5.42
5 participants