0 Fork 0

mirror of https://github.com/carbon-language/carbon-lang.git synced 2026-11-15 10:28:30 +00:00

Files

T

josh11bandJosh L 5406588107 Update member access design docs for proposals #3720 and #7697 (#7823 )

- Incorporates member binding interfaces from proposal #3720
- Includes updates to #3720 and new `x.impl(m)` and `typeof(x)` syntaxes
from #7697
- The concept of member resolution was replaced with just its name
lookup component, to reflect the new rules from #7697
- Updated member binding interfaces use of `extend` according to
proposal #5337
- `BindToRef` interface updated to use `ref` following proposal #5434

Assisted-by: Gemini via Antigravity

---------

Co-authored-by: Josh L <josh11b@users.noreply.github.com>

2026-10-01 20:18:37 +00:00

design

Update member access design docs for proposals #3720 and #7697 (#7823 )

2026-10-01 20:18:37 +00:00

guides

Fix minor grammatical error in docs (#3537 )

2023-12-21 22:05:47 +00:00

images

Systematically update syntax in the design for #7254 (#7259 )

2026-07-07 00:41:06 +00:00

project

Add a jj push wrapper that runs prek before pushing. (#7805 )

2026-09-18 19:40:25 +00:00

spec

Initial rough framework for specification. (#140 )

2022-03-16 15:43:09 -07:00

README.md

Remove references to explorer (#5287 )

2025-04-10 22:05:45 +00:00

README.md

Docs

This directory contains current, accepted documentation underpinning Carbon. These documents cover all aspects of Carbon ranging from the project down to detailed designs for specific language features.

If you're trying to learn more about Carbon, we recommend starting at /README.md.

Design

Carbon language's design and rationale are documented in the design/ directory. This documentation is intended to support the following audiences:

People who wish to determine whether Carbon would be the right choice for a project compared to other existing languages.
People working on the evolution of the Carbon language who wish to understand the rationale and motivation for existing design decisions.
People working on a specification or implementation of the Carbon language who need a detailed understanding of the intended design.
People writing Carbon code who wish to understand why the language rules are the way they are.

This is in contrast to proposals, which document the individual decisions that led to this design (along with other changes to the Carbon project), including the rationale and alternatives considered.

Project

The project/ directory contains project-related documentation for Carbon, including:

goals, and the principles and roadmap derived from those goals,
how the project works, and
how to contribute.

Guides

The guides/ directory contains to-be-written end-user documentation for developers writing programs in Carbon.

Spec

The spec/ directory contains the to-be-written formal specification of the Carbon language. This is for implementers of compilers or other tooling. This is intended to complement the toolchain.