ci: fix clite init() causing linting failure

[MeteorsLiu]

No description provided.

[niupilot]

PR Review Complete ✅

Todo List:

• Read repository guidelines (CLAUDE.md)
• Examine the changed file: _demo/go/export/libexport.h.want
• Analyze the diff to understand what was added
• Review code quality and potential issues
• Check for documentation consistency
• Provide comprehensive review feedback

---

Review Summary

This PR adds a single missing initialization function declaration to the expected C header file libexport.h.want. The change is minimal but important for maintaining consistency.

Detailed Analysis

🔍 What Changed

The PR adds 3 lines at lines 282-284 in _demo/go/export/libexport.h.want:

void
github.com_goplus_llgo_runtime_internal_clite_init(void) GO_SYMBOL_RENAME("github.com/goplus/llgo/runtime/internal/clite.init")

✅ Positive Aspects

1. Consistent Pattern: The added function follows the exact same pattern as other init functions in the file:

   • Uses the standardized naming convention for Go package init functions
   • Proper GO_SYMBOL_RENAME macro usage for cross-platform symbol handling
   • Consistent C function declaration syntax

2. Proper Placement: The function is added in the correct alphabetical order within the init functions section (between runtime/abi.init and runtime/internal/clite/bdwgc.init)

3. No Breaking Changes: This is purely additive - no existing functionality is modified

🎯 Technical Assessment

Code Quality: ✅ Excellent

• Follows established conventions perfectly
• No syntax errors or formatting issues
• Proper use of the GO_SYMBOL_RENAME macro for platform-specific symbol handling

Potential Issues: ✅ None Identified

• The change is minimal and low-risk
• No memory management concerns
• No API compatibility issues

Architecture: ✅ Consistent

• Maintains the existing pattern of exporting Go runtime init functions to C
• Fits well within the llgo's FFI (Foreign Function Interface) architecture

📚 Documentation Consistency

The change doesn't require documentation updates since:

• It's adding a missing init function that should have been there
• The file is auto-generated (as indicated by the header comment: /* Code generated by llgo; DO NOT EDIT. */)
• The purpose is to fix CI checks, as indicated by the branch name fix-export-check-ci

🔧 Context & Purpose

This appears to be fixing a CI issue where the generated header didn't match the expected output. The missing clite.init function likely caused test failures. This is a maintenance fix rather than a new feature.

📋 Recommendations

1. ✅ Approve: This is a straightforward fix that adds a missing initialization function
2. ✅ No additional changes needed: The change is minimal and correct
3. ✅ Safe to merge: No risk of breaking existing functionality

---

Overall Assessment: This is a well-executed maintenance fix that resolves a CI issue by adding a missing initialization function declaration. The implementation follows all established patterns and conventions perfectly.

👉 Want me to re-run this review? Just type /review in the comments! For more usage examples, visit CodeAgent GitHub Repository.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.10%. Comparing base (897f944) to head (e4f77f0).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1299   +/-   ##
=======================================
  Coverage   90.10%   90.10%           
=======================================
  Files          43       43           
  Lines       12562    12562           
=======================================
  Hits        11319    11319           
  Misses       1087     1087           
  Partials      156      156           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.