Deprecate always 1 CRYPT_ constants
#10773
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is already covered by https://wiki.php.net/rfc/deprecations_php_8_3 so IMO no need for a separate RFC. However, the implementation may come in handy later. |
|
Please link this PR in the RFC you linked and delete my RFC. |
Linking is done, but I cannot delete the RFC. Having URLs is cheap so I don't mind it. |
|
This part of the deprecation RFC was not accepted. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The constant does not imply any value, they just slow php startup.
RFC: https://wiki.php.net/rfc/deprecate-unuseful-crypt-constants