only skip hash keys sorting for actually tied hashes #42
Conversation
This file contains 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
|
Testing in branch |
|
Rebased into release 3.0201 |
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.
As of version 2.25, JSON::XS announced that it won't sort tied hashes under the 'canonical' option. But it's implementation covered too broad range of magic - SvRMAGICAL is set for any magic other then mg_get/mg_set upon cast.
It was discovered in the garu/Data-Printer#75 issue that the core module Hash::Util::FieldHash can easily produce hashes that won't be sorted by JSON::XS::encode_json despite being not tie'd.