Skip to content

cherry-pick: add nameconst #25001

Open
daviszhen wants to merge 2 commits into
matrixorigin:4.0-devfrom
daviszhen:0616-pick-main-to-4.0-001dd8f
Open

cherry-pick: add nameconst #25001
daviszhen wants to merge 2 commits into
matrixorigin:4.0-devfrom
daviszhen:0616-pick-main-to-4.0-001dd8f

Conversation

@daviszhen

Copy link
Copy Markdown
Contributor

What type of PR is this?

  • API-change
  • BUG
  • Improvement
  • Documentation
  • Feature
  • Test and CI
  • Code Refactoring

Which issue(s) this PR fixes:

issue #24486

What this PR does / why we need it:

增加name_const函数

@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@XuPeng-SH XuPeng-SH left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed with extra unhappy-path focus.

This 4.0-dev cherry-pick matches the NAME_CONST behavior I already checked on the mainline PR: the binder still rejects non-literal/cast/function/column argument shapes at the AST-validation stage, and the heading propagation / alias behavior is covered by the added unit tests and BVT. I did not find a new blocking issue introduced by the cherry-pick itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/enhancement size/L Denotes a PR that changes [500,999] lines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants