PHP 7.4: Custom object serialization RFC #868
Merged
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
> A new mechanism for custom object serialization has been added, which uses two new magic methods: > > ```php > // Returns array containing all the necessary state of the object. > public function __serialize(): array; > > // Restores the object state from the given data array. > public function __unserialize(array $data): void; > ``` > > The new serialization mechanism supersedes the Serializable interface, which will be deprecated in the future. Refs: * https://wiki.php.net/rfc/custom_object_serialization * https://github.com/php/php-src/blob/3775d47eee38f3b34f800a0b23f840ec7a94e4c7/UPGRADING#L305-L315 * php/php-src#3761 * php/php-src@d373c11 Includes unit tests. Related to 808
From the RFC: > **Creating objects in __unserialize()** > > Some people have expressed a desire to make __unserialize() a static method which creates and returns the unserialized object (rather than first constructing the object and then calling __unserialize() to initialize it). > > This would allow an even greater degree of control over the serialization mechanism, for example it would allow to return an already existing object from __unserialize(). > > However, allowing this would once again require immediately calling __unserialize() functions (interleaved with unserialization) to make the object available for backreferences, which would reintroduce some of the problems that Serializable suffers from. As such, this will not be supported. Refs: * https://wiki.php.net/rfc/custom_object_serialization * https://github.com/php/php-src/blob/3775d47eee38f3b34f800a0b23f840ec7a94e4c7/UPGRADING#L305-L315 * php/php-src#3761 * php/php-src@d373c11 Includes unit tests. Related to 808
40 tasks
wimg
approved these changes
Aug 26, 2019
delete-merged-branch
bot
deleted the
php-7.4/custom-object-serialization
branch
jrfnl
removed
PR: ready for review
PR: quick merge
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.
PHP 7.4/NewMagicMethods: handle new __(un)serialize()
Refs:
Includes unit tests.
PHP 7.4/NonStaticMagicMethods: handle new __(un)serialize()
From the RFC:
Refs:
Includes unit tests.
Related to #808