chaokunyang opened a new pull request, #3469:
URL: https://github.com/apache/fory/pull/3469

   <!--
   **Thanks for contributing to Apache Fory™.**
   
   **If this is your first time opening a PR on fory, you can refer to 
[CONTRIBUTING.md](https://github.com/apache/fory/blob/main/CONTRIBUTING.md).**
   
   Contribution Checklist
   
       - The **Apache Fory™** community has requirements on the naming of pr 
titles. You can also find instructions in 
[CONTRIBUTING.md](https://github.com/apache/fory/blob/main/CONTRIBUTING.md).
   
       - Apache Fory™ has a strong focus on performance. If the PR you submit 
will have an impact on performance, please benchmark it first and provide the 
benchmark result here.
   -->
   
   ## Why?
   
   <!-- Describe the purpose of this PR. -->
   
   ## What does this PR do?
   
   <!-- Describe the details of this PR. -->
   
   ## Related issues
   
   <!--
   Is there any related issue? If this PR closes them you say say fix/closes:
   
   - #xxxx0
   - #xxxx1
   - Fixes #xxxx2
   -->
   
   ## AI Contribution Checklist (required when AI assistance = `yes`)
   
   <!-- Please read: 
https://github.com/apache/fory/blob/main/AI_CONTRIBUTION_POLICY.md -->
   <!-- Mark `yes` when AI materially influenced technical content.
   Examples: non-trivial code/test logic generated by AI (even one function), 
about 20+ added/changed lines influenced by AI, or AI influence on 
API/protocol/performance/architecture decisions.
   Mark `no` for minor/narrow assistance only 
(spelling/grammar/formatting/trivial comment or wording edits with no behavior 
impact). -->
   
   - [ ] Substantial AI assistance was used in this PR: `yes` / `no`
   - [ ] If `yes`, I included the standardized AI Usage Disclosure block below.
   - [ ] If `yes`, I can explain and defend all important changes without AI 
help.
   - [ ] If `yes`, I reviewed AI-assisted code changes line by line before 
submission.
   - [ ] If `yes`, I ran adequate human verification and recorded evidence 
(checks run locally or in CI, pass/fail summary, and confirmation I reviewed 
results).
   - [ ] If `yes`, I added/updated tests and specs where required.
   - [ ] If `yes`, I validated protocol/performance impacts with evidence when 
applicable.
   - [ ] If `yes`, I verified licensing and provenance compliance.
   
   AI Usage Disclosure (only when substantial AI assistance = `yes`):
   
   <!-- Use this standard template to keep reviews consistent and low-overhead. 
-->
   
   ```text
   AI Usage Disclosure
   - substantial_ai_assistance: yes
   - scope: <design drafting | code drafting | refactor suggestions | tests | 
docs | other>
   - affected_files_or_subsystems: <high-level paths/modules>
   - human_verification: <checks run locally or in CI + pass/fail summary + 
contributor reviewed results>
   - performance_verification: <N/A or benchmark/regression evidence summary>
   - provenance_license_confirmation: <Apache-2.0-compatible provenance 
confirmed; no incompatible third-party code introduced>
   ```
   
   ## Does this PR introduce any user-facing change?
   
   <!--
   If any user-facing interface changes, please [open an 
issue](https://github.com/apache/fory/issues/new/choose) describing the need to 
do so and update the document if necessary.
   
   Delete section if not applicable.
   -->
   
   - [ ] Does this PR introduce any public API change?
   - [ ] Does this PR introduce any binary protocol compatibility change?
   
   ## Benchmark
   
   <!--
   When the PR has an impact on performance (if you don't know whether the PR 
will have an impact on performance, you can submit the PR first, and if it will 
have impact on performance, the code reviewer will explain it), be sure to 
attach a benchmark data here.
   
   Delete section if not applicable.
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to