Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[VarExporter] Leverage native lazy objects#59890

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

nicolas-grekas
Copy link
Member

@nicolas-grekasnicolas-grekas commentedMar 2, 2025
edited
Loading

QA
Branch?7.3
Bug fix?no
New feature?yes
Deprecations?no
Issues-
LicenseMIT

Let's leverage native lazy objects.

Instead of keeping/updating LazyGhostTrait and LazyProxyTrait, I'm deprecating them in favor of using native lazy proxies directly.

There is one use case that is not covered by native lazy objects: lazy decorators - aka lazy proxies built against an interface or an internal class. For this use case, we keepProxyHelper::generateLazyProxy().

GromNaN reacted with heart emojimtarld, chalasr, arnaud-lb, jdreesen, GromNaN, and dmaicher reacted with rocket emoji
@carsonbotcarsonbot added this to the7.3 milestoneMar 2, 2025
@nicolas-grekasnicolas-grekasforce-pushed theve-native-lazy-objects branch 2 times, most recently fromae65a7a to3b27972CompareMarch 3, 2025 09:45
@nicolas-grekasnicolas-grekasforce-pushed theve-native-lazy-objects branch 2 times, most recently from0bbd405 to7badfb5CompareMarch 14, 2025 16:44
@nicolas-grekas

This comment was marked as outdated.

@nicolas-grekasnicolas-grekasforce-pushed theve-native-lazy-objects branch 2 times, most recently from9852544 to1d14933CompareMarch 15, 2025 13:04
@nicolas-grekasnicolas-grekas mentioned this pull requestMar 15, 2025
nicolas-grekas added a commit that referenced this pull requestMar 15, 2025
This PR was merged into the 7.3 branch.Discussion----------Various cleanups| Q             | A| ------------- | ---| Branch?       | 7.3| Bug fix?      | no| New feature?  | no| Deprecations? | no| Issues        | -| License       | MITFound while working on#59890Commits-------18390f1 Various cleanups
@nicolas-grekas
Copy link
MemberAuthor

nicolas-grekas commentedMar 15, 2025
edited
Loading

Self-review:

Status: needs work

@stof
Copy link
Member

Be careful. Doctrine ORM 2.x is not EOL yet and it already supports using var-exporter (but will probably not receive a backport of the support for native lazy objects). This might impact the deprecation plan.

@nicolas-grekasnicolas-grekasforce-pushed theve-native-lazy-objects branch 4 times, most recently from6b9b1fd toe382b2fCompareMarch 21, 2025 15:56
@nicolas-grekas
Copy link
MemberAuthor

Doctrine ORM 2.x is not EOL yet and it already supports using var-exporter (but will probably not receive a backport of the support for native lazy objects). This might impact the deprecation plan.

I don't think this should impact us: ppl have a way to fix the deprecation: upgrade. The day where 2.x will be EOLed is close anyway.

After many error-n-trial, I just pushed what I think is the implementation that works. First I thought we could use hooks to proxy all properties, but it happens those are not really compatible with references, so that we have to keep using magic accessors to proxy them.

Status: needs review

@nicolas-grekasnicolas-grekas merged commit4bcf132 intosymfony:7.3Mar 22, 2025
7 of 10 checks passed
@nicolas-grekasnicolas-grekas deleted the ve-native-lazy-objects branchMarch 22, 2025 17:12
@fabpotfabpot mentioned this pull requestMay 2, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Projects
None yet
Milestone
7.3
Development

Successfully merging this pull request may close these issues.

3 participants
@nicolas-grekas@stof@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp