[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-1290":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":22,"hasPages":24,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":28,"readmeContent":29,"aiSummary":30,"trendingCount":16,"starSnapshotCount":16,"syncStatus":19,"lastSyncTime":31,"discoverSource":32},1290,"styleguide","google\u002Fstyleguide","google","Style guides for Google-originated open-source projects","https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002F",null,"HTML",39360,12970,1249,119,0,10,86,2,83.6,"Other",false,"gh-pages",true,[26,27,5],"cpplint","style-guide","2026-06-12 04:00:08","# Google Style Guides\n\nEvery major open-source project has its own style guide: a set of conventions\n(sometimes arbitrary) about how to write code for that project. It is much\neasier to understand a large codebase when all the code in it is in a consistent\nstyle.\n\n“Style” covers a lot of ground, from “use camelCase for variable names” to\n“never use global variables” to “never use exceptions.” This project\n([google\u002Fstyleguide](https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fstyleguide)) links to the style\nguidelines we use for Google code. If you are modifying a project that\noriginated at Google, you may be pointed to this page to see the style guides\nthat apply to that project.\n\n\n*   [AngularJS Style Guide][angular]\n*   [Common Lisp Style Guide][cl]\n*   [C++ Style Guide][cpp]\n*   [C# Style Guide][csharp]\n*   [Go Style Guide][go]\n*   [HTML\u002FCSS Style Guide][htmlcss]\n*   [JavaScript Style Guide][js]\n*   [Java Style Guide][java]\n*   [JSON Style Guide][json]\n*   [Markdown Style Guide][markdown]\n*   [Objective-C Style Guide][objc]\n*   [Python Style Guide][py]\n*   [R Style Guide][r]\n*   [Shell Style Guide][sh]\n*   [Swift Style Guide][swift]\n*   [TypeScript Style Guide][ts]\n*   [Vim script Style Guide][vim]\n\nThis project also contains [google-c-style.el][emacs], an Emacs settings file\nfor Google style.\n\nWe used to host the cpplint tool, but we stopped making internal updates public.\nAn open source community has forked the project, so users are encouraged to use\nhttps:\u002F\u002Fgithub.com\u002Fcpplint\u002Fcpplint instead.\n\nIf your project requires that you create a new XML document format, the\n[XML Document Format Style Guide][xml] may be helpful. In addition to actual\nstyle rules, it also contains advice on designing your own vs. adapting an\nexisting format, on XML instance document formatting, and on elements vs.\nattributes.\n\nThe style guides in this project are licensed under the CC-By 3.0 License, which\nencourages you to share these documents. See\n[https:\u002F\u002Fcreativecommons.org\u002Flicenses\u002Fby\u002F3.0\u002F][ccl] for more details.\n\nThe following Google style guide lives outside of this project:\n\n*  [Effective Dart][dart]\n*  [Kotlin Style Guide][kotlin]\n\nSince projects are largely maintained in a [VCS], writing good commit messages\nis important to long term project health. Please refer to [How to Write a Git\nCommit Message](https:\u002F\u002Fcbea.ms\u002Fgit-commit\u002F) as an excellent resource. While it\nexplicitly refers to the Git [SCM], its principles apply to any system, and many\nGit conventions are trivial to translate to others.\n\n## Contributing\n\nWith few exceptions, these style guides are copies of Google's internal style\nguides to assist developers working on Google owned and originated open source\nprojects. Changes to the style guides are made to the internal style guides\nfirst and eventually copied into the versions found here. **External\ncontributions are not accepted.** Pull requests are regularly closed without\ncomment.\n\nPeople can file [issues using the GitHub tracker][gh-tracker]. Issues that raise\nquestions, justify changes on technical merits, or point out obvious mistakes\nmay get some engagement and could in theory lead to changes, but we are\nprimarily optimizing for Google's internal needs.\n\n\u003Ca rel=\"license\" href=\"https:\u002F\u002Fcreativecommons.org\u002Flicenses\u002Fby\u002F3.0\u002F\">\u003Cimg alt=\"Creative Commons License\" style=\"border-width:0\" src=\"https:\u002F\u002Fi.creativecommons.org\u002Fl\u002Fby\u002F3.0\u002F88x31.png\" \u002F>\u003C\u002Fa>\n\n[cpp]: https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fcppguide.html\n[csharp]: https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fcsharp-style.html\n[swift]: https:\u002F\u002Fgoogle.github.io\u002Fswift\u002F\n[objc]: objcguide.md\n[gh-tracker]: https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fstyleguide\u002Fissues\n[go]: go\u002F\n[java]: https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fjavaguide.html\n[json]: https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fjsoncstyleguide.xml\n[kotlin]: https:\u002F\u002Fdeveloper.android.com\u002Fkotlin\u002Fstyle-guide\n[py]: https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fpyguide.html\n[r]: https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002FRguide.html\n[sh]: https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fshellguide.html\n[htmlcss]: https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fhtmlcssguide.html\n[js]: https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fjsguide.html\n[markdown]: https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fdocguide\u002Fstyle.html\n[ts]: https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Ftsguide.html\n[angular]: https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fangularjs-google-style.html\n[cl]: https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Flispguide.xml\n[vim]: https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fvimscriptguide.xml\n[emacs]: https:\u002F\u002Fraw.githubusercontent.com\u002Fgoogle\u002Fstyleguide\u002Fgh-pages\u002Fgoogle-c-style.el\n[xml]: https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fxmlstyle.html\n[dart]: https:\u002F\u002Fwww.dartlang.org\u002Fguides\u002Flanguage\u002Feffective-dart\n[ccl]: https:\u002F\u002Fcreativecommons.org\u002Flicenses\u002Fby\u002F3.0\u002F\n[SCM]: https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FSource_control_management\n[VCS]: https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FVersion_control_system\n","google\u002Fstyleguide 项目提供了针对 Google 开源项目的编程风格指南。该项目涵盖了多种编程语言和工具的风格建议，如 C++、Java、Python 等，并且包含了详细的编码规范和最佳实践，帮助开发者编写一致且高质量的代码。它特别适用于那些基于 Google 源头的开源项目或希望遵循 Google 编码标准的新项目。通过使用这些指南，团队可以提高代码可读性和维护性，确保项目中的代码风格统一。","2026-06-11 02:42:49","top_all"]