[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-1815":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":24,"hasPages":24,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":32,"readmeContent":33,"aiSummary":34,"trendingCount":16,"starSnapshotCount":16,"syncStatus":35,"lastSyncTime":36,"discoverSource":37},1815,"carbon-lang","carbon-language\u002Fcarbon-lang","carbon-language","Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)","http:\u002F\u002Fdocs.carbon-lang.dev\u002F",null,"C++",33792,1535,387,203,0,74,120,7,44.56,"Other",false,"trunk",true,[5,26,27,28,29,30,31],"compiler","cpp","experimental","experimental-language","language","programming-language","2026-06-12 02:00:33","# Carbon Language: \u003Cbr\u002F> An experimental successor to C++\n\n\u003C!--\nPart of the Carbon Language project, under the Apache License v2.0 with LLVM\nExceptions. See \u002FLICENSE for license information.\nSPDX-License-Identifier: Apache-2.0 WITH LLVM-exception\n-->\n\n\u003Cp align=\"center\">\n  \u003Ca href=\"#why-build-carbon\">Why?\u003C\u002Fa> |\n  \u003Ca href=\"#language-goals\">Goals\u003C\u002Fa> |\n  \u003Ca href=\"#project-status\">Status\u003C\u002Fa> |\n  \u003Ca href=\"#getting-started\">Getting started\u003C\u002Fa> |\n  \u003Ca href=\"#join-us\">Join us\u003C\u002Fa>\n\u003C\u002Fp>\n\n**See our [announcement video](https:\u002F\u002Fyoutu.be\u002FomrY53kbVoA) from\n[CppNorth](https:\u002F\u002Fcppnorth.ca\u002F).** Note that Carbon is\n[not ready for use](#project-status).\n\n\u003Ca href=\"docs\u002Fimages\u002Fsnippets.md#quicksort\">\n\u003C!--\nEdit snippet in docs\u002Fimages\u002Fsnippets.md and:\nhttps:\u002F\u002Fdrive.google.com\u002Fdrive\u002Ffolders\u002F1QrBXiy_X74YsOueeC0IYlgyolWIhvusB\n-->\n\u003Cimg src=\"docs\u002Fimages\u002Fquicksort_snippet.svg\" align=\"right\" width=\"575\"\n     alt=\"Quicksort code in Carbon. Follow the link to read more.\">\n\u003C\u002Fa>\n\n\u003C!--\nDon't let the text wrap too narrowly to the left of the above image.\nThe `div` reduces the vertical height. The `picture` prevents autolinking.\n-->\n\u003Cdiv>\u003Cpicture>\u003Cimg src=\"docs\u002Fimages\u002Fbumper.png\" alt=\"\">\u003C\u002Fpicture>\u003C\u002Fdiv>\n\n**Fast and works with C++**\n\n-   Performance matching C++ using LLVM, with low-level access to bits and\n    addresses\n-   Interoperate with your existing C++ code, from inheritance to templates\n-   Fast and scalable builds that work with your existing C++ build systems\n\n**Modern and evolving**\n\n-   Solid language foundations that are easy to learn, especially if you have\n    used C++\n-   Easy, tool-based upgrades between Carbon versions\n-   Safer fundamentals, and an incremental path towards a memory-safe subset\n\n**Welcoming open-source community**\n\n-   Clear goals and priorities with robust governance\n-   Community that works to be welcoming, inclusive, and friendly\n-   Batteries-included approach: compiler, libraries, docs, tools, package\n    manager, and more\n\n## Why build Carbon?\n\nC++ remains the dominant programming language for performance-critical software,\nwith massive and growing codebases and investments. However, it is struggling to\nimprove and meet developers' needs, as outlined above, in no small part due to\naccumulating decades of technical debt. Incrementally improving C++ is\n[extremely difficult](\u002Fdocs\u002Fproject\u002Fdifficulties_improving_cpp.md), both due to\nthe technical debt itself and challenges with its evolution process. The best\nway to address these problems is to avoid inheriting the legacy of C or C++\ndirectly, and instead start with solid language foundations like\n[modern generics system](#generics), modular code organization, and consistent,\nsimple syntax.\n\nExisting modern languages already provide an excellent developer experience: Go,\nSwift, Kotlin, Rust, and many more. **Developers that _can_ use one of these\nexisting languages _should_.** Unfortunately, the designs of these languages\npresent significant barriers to adoption and migration from C++. These barriers\nrange from changes in the idiomatic design of software to performance overhead.\n\nCarbon is fundamentally **a successor language approach**, rather than an\nattempt to incrementally evolve C++. It is designed around interoperability with\nC++ as well as large-scale adoption and migration for existing C++ codebases and\ndevelopers. A successor language for C++ requires:\n\n-   **Performance matching C++**, an essential property for our developers.\n-   **Seamless, bidirectional interoperability with C++**, such that a library\n    anywhere in an existing C++ stack can adopt Carbon without porting the rest.\n-   **A gentle learning curve** with reasonable familiarity for C++ developers.\n-   **Comparable expressivity** and support for existing software's design and\n    architecture.\n-   **Scalable migration**, with some level of source-to-source translation for\n    idiomatic C++ code.\n\nWith this approach, we can build on top of C++'s existing ecosystem, and bring\nalong existing investments, codebases, and developer populations. There are a\nfew languages that have followed this model for other ecosystems, and Carbon\naims to fill an analogous role for C++:\n\n-   JavaScript → TypeScript\n-   Java → Kotlin\n-   C++ → **_Carbon_**\n\n## Language Goals\n\nWe are designing Carbon to support:\n\n-   Performance-critical software\n-   Software and language evolution\n-   Code that is easy to read, understand, and write\n-   Practical safety and testing mechanisms\n-   Fast and scalable development\n-   Modern OS platforms, hardware architectures, and environments\n-   Interoperability with and migration from existing C++ code\n\nWhile many languages share subsets of these goals, what distinguishes Carbon is\ntheir combination.\n\nWe also have explicit _non-goals_ for Carbon, notably including:\n\n-   A stable\n    [application binary interface](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FApplication_binary_interface)\n    (ABI) for the entire language and library\n-   Perfect backwards or forwards compatibility\n\nOur detailed [goals](\u002Fdocs\u002Fproject\u002Fgoals.md) document fleshes out these ideas\nand provides a deeper view into our goals for the Carbon project and language.\n\n## Project status\n\nCarbon Language is currently an experimental project. We are hard at work on a\ntoolchain implementation with compiler and linker. You can try out the current\nstate at [compiler-explorer.com](http:\u002F\u002Fcarbon.compiler-explorer.com\u002F).\n\nWe want to better understand whether we can build a language that meets our\nsuccessor language criteria, and whether the resulting language can gather a\ncritical mass of interest within the larger C++ industry and community.\n\nCurrently, we have fleshed out several core aspects of both Carbon the project\nand the language:\n\n-   The strategy of the Carbon Language and project.\n-   An open-source project structure, governance model, and evolution process.\n-   Critical and foundational aspects of the language design informed by our\n    experience with C++ and the most difficult challenges we anticipate. This\n    includes designs for:\n    -   Generics\n    -   Class types\n    -   Inheritance\n    -   Operator overloading\n    -   Lexical and syntactic structure\n    -   Code organization and modular structure\n-   An under-development [compiler and toolchain](\u002Ftoolchain\u002F) that will compile\n    Carbon (and eventually C++ code as well) into standard executable code. This\n    is where most of our current implementation efforts are directed.\n    -   Historically, there was also a prototype\n        [explorer](https:\u002F\u002Fgithub.com\u002Fcarbon-language\u002Fexplorer) interpreter that\n        implemented an older version of the Carbon language design, but is no\n        longer under development and has been archived.\n\nIf you're interested in contributing, we're currently focused on developing the\nCarbon toolchain until it can\n[support Carbon ↔ C++ interop](\u002Fdocs\u002Fproject\u002Froadmap.md#access-most-non-template-c-apis-in-carbon).\nBeyond that, we plan to continue developing the design and toolchain until we\ncan ship the\n[0.1 language](\u002Fdocs\u002Fproject\u002Fmilestones.md#milestone-01-a-minimum-viable-product-mvp-for-evaluation)\nand support evaluating Carbon in more detail.\n\nYou can see our [full roadmap](\u002Fdocs\u002Fproject\u002Froadmap.md) for more details.\n\n## Carbon and C++\n\nIf you're already a C++ developer, Carbon should have a gentle learning curve.\nIt is built out of a consistent set of language constructs that should feel\nfamiliar and be easy to read and understand.\n\nThe Carbon code here is hypothetical and meant to show the look and feel of the\nlanguage.\n\nC++ code like this:\n\n\u003Ca href=\"docs\u002Fimages\u002Fsnippets.md#c\">\n\u003C!--\nEdit snippet in docs\u002Fimages\u002Fsnippets.md and:\nhttps:\u002F\u002Fdrive.google.com\u002Fdrive\u002Ffolders\u002F1QrBXiy_X74YsOueeC0IYlgyolWIhvusB\n-->\n\u003Cimg src=\"docs\u002Fimages\u002Fcpp_snippet.svg\" width=\"600\"\n     alt=\"A snippet of C++ code. Follow the link to read it.\">\n\u003C\u002Fa>\n\ncorresponds to this Carbon code:\n\n\u003Ca href=\"docs\u002Fimages\u002Fsnippets.md#carbon\">\n\u003C!--\nEdit snippet in docs\u002Fimages\u002Fsnippets.md and:\nhttps:\u002F\u002Fdrive.google.com\u002Fdrive\u002Ffolders\u002F1QrBXiy_X74YsOueeC0IYlgyolWIhvusB\n-->\n\u003Cimg src=\"docs\u002Fimages\u002Fcarbon_snippet.svg\" width=\"600\"\n     alt=\"A snippet of converted Carbon code. Follow the link to read it.\">\n\u003C\u002Fa>\n\nYou can call Carbon from C++ without overhead and the other way around. This\nmeans you migrate a single C++ library to Carbon within an application, or write\nnew Carbon on top of your existing C++ investment. For example:\n\n\u003Ca href=\"docs\u002Fimages\u002Fsnippets.md#mixed\">\n\u003C!--\nEdit snippet in docs\u002Fimages\u002Fsnippets.md and:\nhttps:\u002F\u002Fdrive.google.com\u002Fdrive\u002Ffolders\u002F1QrBXiy_X74YsOueeC0IYlgyolWIhvusB\n-->\n\u003Cimg src=\"docs\u002Fimages\u002Fmixed_snippet.svg\" width=\"600\"\n     alt=\"A snippet of mixed Carbon and C++ code. Follow the link to read it.\">\n\u003C\u002Fa>\n\nRead more about\n[C++ interop in Carbon](\u002Fdocs\u002Fdesign\u002Finteroperability\u002Fphilosophy_and_goals.md).\n\nBeyond interoperability between Carbon and C++, we're also planning to support\nmigration tools that will mechanically translate idiomatic C++ code into Carbon\ncode to help you switch an existing C++ codebase to Carbon.\n\n## Generics\n\nCarbon provides a\n**[modern generics system](\u002Fdocs\u002Fdesign\u002Fgenerics\u002Foverview.md#what-are-generics)**\nwith checked definitions, while still **supporting opt-in\n[templates](\u002Fdocs\u002Fdesign\u002Ftemplates.md) for seamless C++ interop**. Checked\ngenerics provide several advantages compared to C++ templates:\n\n-   **Generic definitions are fully type-checked**, removing the need to\n    instantiate to check for errors and giving greater confidence in code.\n    -   Avoids the compile-time cost of re-checking the definition for every\n        instantiation.\n    -   When using a definition-checked generic, usage error messages are\n        clearer, directly showing which requirements are not met.\n-   **Enables automatic, opt-in type erasure and dynamic dispatch** without a\n    separate implementation. This can reduce the binary size and enables\n    constructs like heterogeneous containers.\n-   **Strong, checked interfaces** mean fewer accidental dependencies on\n    implementation details and a clearer contract for consumers.\n\nWithout sacrificing these advantages, **Carbon generics support\nspecialization**, ensuring it can fully address performance-critical use cases\nof C++ templates. For more details about Carbon's generics, see their\n[design](\u002Fdocs\u002Fdesign\u002Fgenerics).\n\nIn addition to easy and powerful interop with C++, Carbon templates can be\nconstrained and incrementally migrated to checked generics at a fine granularity\nand with a smooth evolutionary path.\n\n## Memory safety\n\nSafety, and especially\n[memory safety](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMemory_safety), remains a key\nchallenge for C++ and something a successor language needs to address.\n\nWe plan to support a two step migration process:\n\n1. Highly automated, minimal supervision migration from C++ to a dialect of\n   Carbon designed for C++ interop and migration.\n2. Incremental refactoring of the Carbon code to adopt memory-safe designs,\n   patterns, and APIs.\n\nWe also want to address important, low-hanging fruit in the safety space\nimmediately when migrating into Carbon:\n\n-   Tracking uninitialized states better, increased enforcement of\n    initialization, and hardening against initialization bugs when needed.\n-   Designing fundamental APIs and idioms to support dynamic bounds checking.\n-   Switching from undefined behavior to erroneous behavior wherever possible,\n    and marking the remaining undefined behavior with visible `unsafe` syntax.\n-   Having a default debug build mode that has less runtime overhead while being\n    more comprehensive than existing C++ debug build modes combined with\n    [Address Sanitizer](https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fsanitizers\u002Fwiki\u002FAddressSanitizer).\n\nFor more details, see our [safety design](\u002Fdocs\u002Fdesign\u002Fsafety).\n\n## Getting started\n\nTo try out Carbon immediately in your browser, you can use the toolchain at:\n[carbon.compiler-explorer.com](http:\u002F\u002Fcarbon.compiler-explorer.com\u002F).\n\nWe are developing a traditional toolchain for Carbon that can compile and link\nprograms. However, Carbon is still an early, experimental project, and so we\nonly have very experimental nightly releases of the Carbon toolchain available\nto download, and only on limited platforms. If you are using a recent Ubuntu\nLinux or similar (Debian, WSL, etc.), you can try these out by going to our\n[releases](https:\u002F\u002Fgithub.com\u002Fcarbon-language\u002Fcarbon-lang\u002Freleases) page and\ndownload the latest nightly toolchain tar file:\n`carbon_toolchain-0.0.0-0.nightly.YYYY.MM.DD.tar.gz`. Then you can try it out:\n\n```shell\n# A variable with the nightly version from yesterday:\nVERSION=\"$(date -d yesterday +0.0.0-0.nightly.%Y.%m.%d)\"\n\n# Get the release\nwget https:\u002F\u002Fgithub.com\u002Fcarbon-language\u002Fcarbon-lang\u002Freleases\u002Fdownload\u002Fv${VERSION}\u002Fcarbon_toolchain-${VERSION}.tar.gz\n\n# Unpack the toolchain:\ntar -xvf carbon_toolchain-${VERSION}.tar.gz\n\n# Create a simple Carbon source file:\necho \"import Core library \\\"io\\\"; fn Run() { Core.Print(42); }\" > forty_two.carbon\n\n# Compile to an object file:\n.\u002Fcarbon_toolchain-${VERSION}\u002Fbin\u002Fcarbon compile \\\n  --output=forty_two.o forty_two.carbon\n\n# Install minimal system libraries used for linking. Note that installing `gcc`\n# or `g++` for compiling C\u002FC++ code with GCC will also be sufficient, these are\n# just the specific system libraries Carbon linking still uses.\nsudo apt install libgcc-11-dev\n\n# Link to an executable:\n.\u002Fcarbon_toolchain-${VERSION}\u002Fbin\u002Fcarbon link \\\n  --output=forty_two forty_two.o\n\n# Run it:\n.\u002Fforty_two\n```\n\nAs a reminder, the toolchain is still very early and many things don't yet work.\nPlease hold off on filing lots of bugs: we know many parts of this don't work\nyet or may not work on all systems. We expect to have releases that are much\nmore robust and reliable that you can try out when we reach our\n[0.1 milestone](\u002Fdocs\u002Fproject\u002Fmilestones.md#milestone-01-a-minimum-viable-product-mvp-for-evaluation).\n\nIf you want to build Carbon's toolchain yourself or are thinking about\ncontributing fixes or improvements to Carbon, you'll need to install our\n[build dependencies](\u002Fdocs\u002Fproject\u002Fcontribution_tools.md#setup-commands) (Clang,\nLLD, libc++) and check out the Carbon repository. For example, on Debian or\nUbuntu:\n\n```shell\n# Update apt.\nsudo apt update\n\n# Install tools.\nsudo apt install \\\n  clang \\\n  libc++-dev \\\n  libc++abi-dev \\\n  lld\n\n# Download Carbon's code.\n$ git clone https:\u002F\u002Fgithub.com\u002Fcarbon-language\u002Fcarbon-lang\n$ cd carbon-lang\n```\n\nThen you can try out our toolchain which has a very early-stage compiler for\nCarbon:\n\n```shell\n# Build and run the toolchain's help to get documentation on the command line.\n$ .\u002Fscripts\u002Frun_bazelisk.py run \u002F\u002Ftoolchain -- help\n```\n\nFor complete instructions, including installing dependencies on various\ndifferent platforms, see our\n[contribution tools documentation](\u002Fdocs\u002Fproject\u002Fcontribution_tools.md).\n\nLearn more about the Carbon project:\n\n-   [Project goals](\u002Fdocs\u002Fproject\u002Fgoals.md)\n-   [Language design overview](\u002Fdocs\u002Fdesign)\n-   [Carbon Toolchain](\u002Ftoolchain)\n-   [FAQ](\u002Fdocs\u002Fproject\u002Ffaq.md)\n\n## Conference talks\n\nCarbon focused talks from the community:\n\n### 2026\n\n-   Benchmarking and optimizing the Carbon compiler, NDC {Toronto} (May 5-8)\n-   Carbon: graduating from the experiment, NDC {Toronto} (May 5-8)\n\n### 2025\n\n-   Carbon: from C++ to Memory Safety, REBASE - ICFP\u002FSPLASH\n    ([slides](https:\u002F\u002Fchandlerc.blog\u002Fslides\u002F2025-rebase-carbon))\n-   Memory safety everywhere with both Carbon and Rust, RustConf\n    ([video](https:\u002F\u002Fyoutu.be\u002FFYLuom6gg_s),\n    [slides](https:\u002F\u002Fchandlerc.blog\u002Fslides\u002F2025-rustconf-memory-safety-everywhere))\n\n### 2024\n\n-   Generic implementation strategies in Carbon and Clang, LLVM Developers'\n    Meeting ([video](https:\u002F\u002Fyoutu.be\u002Fj0BL52NdjAU),\n    [slides](https:\u002F\u002Fchandlerc.blog\u002Fslides\u002F2024-llvm-generic-implementation\u002F#\u002F))\n-   The Carbon Language: Road to 0.1, NDC {TechTown}\n    ([video](https:\u002F\u002Fyoutu.be\u002FbBvLmDJrzvI),\n    [slides](https:\u002F\u002Fchandlerc.blog\u002Fslides\u002F2024-ndc-techtown-carbon-road-to-0-dot-1))\n-   How designing Carbon with C++ interop taught me about C++ variadics and\n    overloads, CppNorth ([video](https:\u002F\u002Fyoutu.be\u002F8SGMy9ENGz8),\n    [slides](https:\u002F\u002Fchandlerc.blog\u002Fslides\u002F2024-cppnorth-design-stories))\n-   Generic Arity: Definition-Checked Variadics in Carbon, C++Now\n    ([video](https:\u002F\u002Fyoutu.be\u002FY_px536l_80),\n    [slides](https:\u002F\u002Fdocs.google.com\u002Fpresentation\u002Fd\u002F10aM1mFMN6Cd5ZkE4OfeiZtSnkVNbo33N-V0et21umww\u002Fedit))\n-   Carbon: An experiment in different tradeoffs, panel session, EuroLLVM\n    ([video](https:\u002F\u002Fyoutu.be\u002FZa_KWj5RMR8),\n    [slides](https:\u002F\u002Fllvm.org\u002Fdevmtg\u002F2024-04\u002Fslides\u002FLightningTalks\u002FSmith-Carbons-high-level-semanticIR.pdf))\n    -   [Alex Bradbury's notes](https:\u002F\u002Fmuxup.com\u002F2024q2\u002Fnotes-from-the-carbon-panel-session-at-eurollvm)\n-   Carbon's high-level semantic IR lightning talk, EuroLLVM\n    ([video](https:\u002F\u002Fyoutu.be\u002FvIWT4RhUcyw))\n\n### 2023\n\n-   Carbon’s Successor Strategy: From C++ interop to memory safety, C++Now\n    ([video](https:\u002F\u002Fyoutu.be\u002F1ZTJ9omXOQ0),\n    [slides](https:\u002F\u002Fchandlerc.blog\u002Fslides\u002F2023-cppnow-carbon-strategy\u002Findex.html#\u002F))\n-   Definition-Checked Generics, C++Now\n    -   Part 1 ([video](https:\u002F\u002Fyoutu.be\u002FFKC8WACSMP0),\n        [slides](https:\u002F\u002Fchandlerc.blog\u002Fslides\u002F2023-cppnow-generics-1\u002F#\u002F))\n    -   Part 2 ([video](https:\u002F\u002Fyoutu.be\u002FVxQ3PwxiSzk),\n        [slides](https:\u002F\u002Fchandlerc.blog\u002Fslides\u002F2023-cppnow-generics-2\u002F#\u002F))\n-   Modernizing Compiler Design for Carbon’s Toolchain, C++Now\n    ([video](https:\u002F\u002Fyoutu.be\u002FZI198eFghJk),\n    [slides](https:\u002F\u002Fchandlerc.blog\u002Fslides\u002F2023-cppnow-compiler\u002Findex.html#\u002F))\n\n### 2022\n\n-   Carbon Language: Syntax and trade-offs, Core C++\n    ([video](https:\u002F\u002Fyoutu.be\u002F9Y2ivB8VaIs),\n    [slides](https:\u002F\u002Fdocs.google.com\u002Fpresentation\u002Fd\u002F1znvL12xCuEfcsP6tpPdrQPnh-UoPFOLnC_RVXZteYaM\u002Fedit))\n-   Carbon Language: An experimental successor to C++, CppNorth\n    ([video](https:\u002F\u002Fyoutu.be\u002FomrY53kbVoA),\n    [slides](https:\u002F\u002Fchandlerc.blog\u002Fslides\u002F2022-07-19-cppnorth-keynote\u002F#\u002F))\n\n### Other videos\n\nWe additionally have [toolchain videos](\u002Ftoolchain\u002Fdocs\u002FREADME.md#videos).\n\n## Join us\n\nWe'd love to have folks join us and contribute to the project. Carbon is\ncommitted to a welcoming and inclusive environment where everyone can\ncontribute.\n\n-   Most of Carbon's design discussions occur on\n    [Discord](https:\u002F\u002Fdiscord.gg\u002FZjVdShJDAs).\n-   To watch for major release announcements, subscribe to our\n    [Carbon release post on GitHub](https:\u002F\u002Fgithub.com\u002Fcarbon-language\u002Fcarbon-lang\u002Fdiscussions\u002F1020)\n    and [star carbon-lang](https:\u002F\u002Fgithub.com\u002Fcarbon-language\u002Fcarbon-lang).\n-   See our [code of conduct](CODE_OF_CONDUCT.md) and\n    [contributing guidelines](CONTRIBUTING.md) for information about the Carbon\n    development community.\n\n### Contributing\n\nYou can also directly:\n\n-   [Contribute to the language design](CONTRIBUTING.md#contributing-to-the-language-design):\n    feedback on design, new design proposal\n-   [Contribute to the language implementation](CONTRIBUTING.md#contributing-to-the-language-implementation)\n    -   [Carbon Toolchain](\u002Ftoolchain\u002F), and project infrastructure\n\nYou can **check out some\n[\"good first issues\"](https:\u002F\u002Fgithub.com\u002Fcarbon-language\u002Fcarbon-lang\u002Flabels\u002Fgood%20first%20issue)**,\nor join the `#contributing-help` channel on\n[Discord](https:\u002F\u002Fdiscord.gg\u002FZjVdShJDAs). See our full\n[`CONTRIBUTING`](CONTRIBUTING.md) documentation for more details.\n","Carbon Language 是一个实验性的 C++ 后继编程语言。它旨在通过提供与 C++ 相匹配的性能、低级位和地址访问能力，以及与现有 C++ 代码（包括继承和模板）的良好互操作性来解决 C++ 的历史遗留问题。Carbon 采用现代语言设计原则，如简洁一致的语法、模块化组织方式及更安全的基础特性，并且支持从旧版本到新版本的工具化平滑升级。此项目适用于需要高性能计算但又希望摆脱 C++ 复杂性和技术债务的应用场景，同时保持与现有 C++ 生态系统的兼容性。",2,"2026-06-11 02:46:12","top_all"]