Skip to content

Cascade merge: 4.x into master - #264

Merged
github-actions[bot] merged 2 commits into
masterfrom
4.x
Nov 11, 2026
Merged

github-actions[bot] merged 2 commits into
masterfrom
4.x

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Automated cascade merge that keeps master in sync with the 4.x maintenance branch.

This PR tracks 4.x and merges automatically once required checks pass, when auto-merge is allowed for the repository; otherwise merge it manually. A new one is opened after each merge, so every future push to 4.x keeps flowing forward into master.

If this PR shows a conflict, resolve it manually on 4.x (or directly on this PR's branch) — auto-merge will pick it up once it's clean again.

claude and others added 2 commits November 11, 2026 22:04
…utoloader

Constructing a ReflectionParameter whose default is a `new` expression
evaluated the default eagerly, and NodeExpressionResolver loaded the class
with include_once of the located file. Reflecting a signature thus declared
a class, bypassing the autoloader: in goaop/framework such a class could
not be woven any more in that process.

- ReflectionParameter resolves its default value on the first access
  (getDefaultValue(), getDefaultValueConstantName(), isDefaultValueConstant(),
  getDefaultValueExpression(), __toString()). The implicit nullability of
  the type is decided on the AST (a literal `null` default), like PHP does at
  compile time, and only constant fetches are evaluated to answer
  isDefaultValueConstant().
- NodeExpressionResolver::loadClassDefinition() loads the class through the
  autoloaders instead of including its file.

Fixes #261

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FxhC1GTbduntXjyF8E9Feb
fix: Resolve parameter defaults lazily and load classes through the autoloader
@github-actions
github-actions Bot merged commit ddbb89b into master Nov 11, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants