Fix json_encode enum repro/compliance — UnitEnum name clash (#6130) - #7801
Merged
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
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.
Summary
VmJson::export()/StringJsonEncodeenum handling was already green on master; repro and VM compliance PHPT failed becauseenum UnitEnumclashes with PHP's built-inUnitEnuminterface (exit 255 beforejson_encoderan).UEin repro + compliance; added JIT compliance PHPT.PHP implementation (already on master)
ext/standard/VmJson.php::exportEnumCase()— unit"", backed scalarlib/JIT/Builtin/StringJsonEncode.php—TYPE_ENUM_CASEbranchC runtime shrink
No new C;
lib/AOT/runtime/remainsphpc_progress.conly.Verification
Output:
Test plan
json_encode_enumVM + JIT compliance filterMade with Cursor