-
Notifications
You must be signed in to change notification settings - Fork 11
feat(internal/config): reduce calling libclang mutiple times #423
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
591882a to
e5616b5
Compare
0aaa2d9 to
ec3dfe8
Compare
|
|
||
| want: "", | ||
| }, | ||
| // FIXME: substring bug |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A Note is recommended to use "MARKER(uid): note body" format.
Details
lint 解释
这个lint结果提示在注释中使用“MARKER(uid): note body”格式是一个建议。这意味着在编写注释时,应该遵循这种特定的格式来提高代码的可读性和一致性。
错误用法
以下是一个错误的示例,展示了不正确的注释格式:
// 这是一个错误的注释格式正确用法
以下是一个正确的示例,展示了符合建议的注释格式:
// MARKER(12345): 这是一个正确的注释格式💡 以上内容由 AI 辅助生成,如有疑问欢迎反馈交流
|
|
||
| want: "testdata/hfile", | ||
| }, | ||
| // FIXME: absolute path |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A Note is recommended to use "MARKER(uid): note body" format.
Details
lint 解释
这个lint结果提示在注释中使用“MARKER(uid): note body”格式是一个推荐的做法。这意味着在编写注释时,应该遵循这种特定的格式来提高代码的可读性和一致性。
错误用法
以下是一个错误的示例,展示了不正确的注释格式:
// 这是一个错误的注释格式正确用法
以下是一个正确的示例,展示了符合推荐格式的注释:
// MARKER(12345): 这是一个正确的注释格式💡 以上内容由 AI 辅助生成,如有疑问欢迎反馈交流
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #423 +/- ##
=======================================
Coverage 84.38% 84.38%
=======================================
Files 27 27
Lines 2728 2728
=======================================
Hits 2302 2302
Misses 385 385
Partials 41 41 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
[Git-flow] Hi @MeteorsLiu, There are some suggestions for your information: Rebase suggestions
Which seems insignificant, recommend to use For other DetailsIf you have any questions about this comment, feel free to raise an issue here: |
No description provided.