mirror of
https://github.com/carbon-language/carbon-lang.git
synced 2026-09-28 19:14:54 +01:00
This catches some common spelling errors, but is *not* an exhaustive spell-checker. The only false positive is "rouge" in Gemfile.lock, which is why I'm excluding that file. True positives are in the change, and it does catch the "langauge" typo I keep making, which zygoloid fixed for me in a few spots. False negatives are: - virmc - Announcemented - propsal For comparison: - cspell (https://www.npmjs.com/package/cspell) is too aggressive and has a small dictionary - Caught the false negatives, but many false positives, including 'LLVM', 'roadmap', 'Carruth' - https://github.com/lorenzwalthert/precommit has a spellcheck, but config looks ruby-specific
23 lines
1.0 KiB
Markdown
23 lines
1.0 KiB
Markdown
# Principles
|
|
|
|
<!--
|
|
Part of the Carbon Language, under the Apache License v2.0 with LLVM
|
|
Exceptions. See /LICENSE for license information.
|
|
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
|
-->
|
|
|
|
Some language [goals](../goals.md) will have widely-applicable, high-impact, and
|
|
sometimes non-obvious corollaries. We collect concrete language design
|
|
principles in this directory as a way to document and clarify these. Principles
|
|
clarify, but do not supersede, goals and priorities. Principles should be used
|
|
as a tool in making decisions, and to clarify to contributors how decisions are
|
|
expected to be made.
|
|
|
|
A key difference between a principle and the design of a language feature is
|
|
that a principle should inform multiple designs, whereas a feature's design is
|
|
typically more focused on achieving a specific goal or set of goals. The
|
|
principle can help achieve consistency across those multiple designs.
|
|
|
|
Note that these principles seek to establish both the approaches the project
|
|
wants to pursue, as well as those we want to exclude.
|