dart-lang/language: the repository where Dart's features are designed before they ship
Design of the Dart language
At a glance
- What is it?
- This is not a Dart library and not the SDK. It is the design repository for the Dart programming language itself, and its contents decide what the compiler will accept years from now.
- Who is it for?
- Adopt a watching brief on dart-lang/language if you maintain Dart tooling, teach the language, or write code that must survive the next two SDK releases: read accepted/ and working/ before you commit to a syntax you cannot migrate away from. Do not clone it expecting a package to depend on, and do not open a feature request without first searching the issue tracker and bringing a motivating example from real code.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly TeX, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- dart-lang/language2,941 ★ · +9
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| dart-lang/language | 2.9k | 2.9k |
9 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What dart-lang/language actually is, and who it is for
The README opens with a plain statement of scope: this repository is the home for the design and evolution of the Dart programming language. That sentence rules out most of what people assume. There is no runtime here, no package to add to pubspec.yaml, and no command that compiles your app. The primary language of the repository is TeX, which is a strong hint about its contents: specifications, formal write-ups, and the prose that eventually becomes normative text.
The audience is correspondingly narrow. Dart application developers will get more from the SDK changelogs than from this repository. The people who belong here are language designers, compiler and analyzer contributors, IDE and linter authors, educators who need to know what is settled versus what is still being argued, and the small group of users who file well-argued feature requests. The README also lists the language team by name as of February 2026, which matters because it tells you who is accountable for reviewing a proposal, and it notes that Erik Ernst maintains the official language specification published on dart.dev, separating the design discussion here from the document that ships as the spec.
One detail in the README is worth reading twice. Contributors are asked to prefer a thumbs-up reaction over a supportive comment, because reactions are easier for the team to aggregate as demand. That is an unusual instruction and it tells you how the repository is used in practice: as a demand-tracking surface, not a chat room.
The life of a language feature, from issue to accepted directory
The README points to a defined process document, doc/life_of_a_language_feature.md, and to a language funnel project board that shows features being actively worked on. The repository layout mirrors that process. The top level contains accepted/, working/, inactive/, archive/, specification/, doc/, templates/, tools/, resources/, lean/ and a few build-related directories.
That directory structure is the mechanism. A feature does not go from idea to shipped syntax in one step. It moves through stages, and the directory a document lives in is the visible record of which stage it has reached. accepted/ holds proposals that the team has agreed to pursue. working/ holds material still under construction. inactive/ and archive/ hold things that stalled or were superseded, and their presence is a reminder that a proposal sitting in the repository is not a commitment to implement it. The templates/ directory exists so that new proposals arrive in a consistent shape, and tools/ and resources/ support the writing and checking of that material rather than the language runtime.
For a reader outside the team, this is the useful part. If you want to know whether a syntax you saw in a blog post is real, the directory tells you more than the prose does. A document in accepted/ has cleared review. A document in working/ has not. Nothing in the repository layout promises a release date, and the README does not describe one.
Installing nothing: how to read dart-lang/language locally
There are no install steps in the README, because there is nothing to install. The repository is a document collection. What you can do is clone it and read it offline, which is genuinely useful when you are comparing several proposals and do not want to page through the web UI.
Clone the default branch:
git clone https://github.com/dart-lang/language.git
cd languageAfter that, the directory listing is your map. The README describes the repository as following a defined process, and the process document sits alongside the proposals:
ls
ls accepted working inactive docThe first listing shows the top-level entries named above. The second shows the contents of the stage directories plus the process document. The README gives no build command and no test command for the repository as a whole, and the analysis_options.yaml at the top level relates to the Dart tooling in tools/, not to a package you would run against your own project.
If you want to participate rather than read, the README sends you to the issue tracker on this repository and sets three expectations: search for an existing issue before filing, bring motivating examples from real world code, and explain why a borrowed feature from another language fits Dart specifically. The README's own phrasing is that the team wants Dart to be the best Dart, not the second-best Rust or Haskell or TypeScript.
Where this repository is the wrong tool
The most common mistake is treating dart-lang/language as a source of truth about current behaviour. It is a source of truth about intended behaviour, and those diverge constantly. A proposal can be accepted and still be unimplemented. A proposal can be in working/ for a long time and then move to inactive/. The README does not document rollback, and it does not promise that anything in accepted/ will ship in a particular version, so anyone quoting a document from this repository as evidence that a feature exists today is overreading it.
The second failure mode is procedural. The README asks contributors to avoid duplicate or near-duplicate issues because they divide attention and make both less visible. A drive-by feature request that ignores that instruction is likely to be closed rather than discussed. The same applies to proposals that amount to wanting another language's feature without an argument for why it fits Dart.
Finally, this is not where you learn the language. If you want to write Dart, the specification link in the README points to dart.dev, and the design discussions here assume you already know the language well enough to reason about type inference and nullability. Reading the repository as a tutorial will be slow and unrewarding.
How it compares with a language specification repository
The natural alternative is the official Dart language specification, which the README links at dart.dev/guides/language/spec and credits Erik Ernst with maintaining. The two serve different readers, and the difference is not cosmetic.
The specification is a normative document describing what the language is. It is written to be cited and to settle disputes about behaviour. This repository is where the arguments happen before that text exists: issue threads, proposal documents, stage directories, and a funnel board tracking what is in flight. The specification has one voice and a stable structure. dart-lang/language has many authors, a templates/ directory to keep their proposals comparable, and an archive of ideas that went nowhere.
If you need to know what a program does, read the specification. If you need to know what the team is considering, whether a feature is still alive, or how to argue for a change, read this repository. Confusing the two leads to the same error described above, quoting a design document as if it were normative text.
Maintenance, licence and the cost of tracking a moving design
The repository is not archived, and the last push was on 2026-09-18, which is recent enough that the design work is ongoing. The repository has no published GitHub releases, which is consistent with its nature: documents are updated in place rather than versioned and published. That has a direct cost. If you cite a document from accepted/ or working/ in your own writing, the file can change under you, and there is no changelog to tell you what moved. Pinning to a commit hash is the only stable reference available, and the README does not suggest one.
On licensing, the README points to two files, LICENSE and PATENTS, and the repository's licence is reported as NOASSERTION, meaning no standard identifier was detected. The PATENTS file is the more interesting of the two for anyone planning to implement or reimplement anything described here, since patent grants are a separate question from copyright. Read both files directly rather than relying on the repository's licence label, and treat this as a question for your own counsel rather than something the README answers.
Editorial conclusion
Adopt a watching brief on dart-lang/language if you maintain Dart tooling, teach the language, or write code that must survive the next two SDK releases: read accepted/ and working/ before you commit to a syntax you cannot migrate away from. Do not clone it expecting a package to depend on, and do not open a feature request without first searching the issue tracker and bringing a motivating example from real code. Verify two things before relying on any document in the repository: which directory the document sits in, since accepted/, working/, inactive/ and archive/ carry different weight, and whether the corresponding change has actually landed in an SDK release you can install.
Frequently asked questions
Is dart-lang/language the Dart SDK or a package I can install?
Neither. The README describes it as the home for the design and evolution of the Dart programming language, and the repository contains documents such as specification material, proposal templates and stage directories rather than runnable code you would depend on.
How do I propose a change to the Dart language?
The README directs you to the issue tracker on this repository and asks you to search for an existing issue first, since duplicates divide attention. It also asks that proposals include motivating examples from real world code and an argument for why the feature suits Dart specifically.
What do the accepted, working and inactive directories mean?
They are the visible stages of the process the README links to in doc/life_of_a_language_feature.md. accepted/ holds proposals the team has agreed to pursue, working/ holds material still under construction, and inactive/ and archive/ hold material that stalled or was superseded.
Does a document in accepted/ mean the feature is available in Dart today?
No. The repository records design decisions, and the README does not promise that anything in accepted/ ships in a particular release or document a rollback path. For current behaviour, the README points to the official language specification at dart.dev.
Who maintains the official Dart language specification?
The README states that Erik Ernst maintains the official language specification, linked at dart.dev/guides/language/spec, separately from the design discussions held in this repository.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/dart-lang-language)Star history chart for your README
[](https://hysenlabs.com/projects/dart-lang-language)Was this useful?