|
|
преди 4 години | |
|---|---|---|
| .. | ||
| README.md | a768b0ee19 Adjust copyrights based on carbon-project-tools/#3 (#171) | преди 5 години |
| error_handling.md | 6639a915dc Principle: Errors are values (#301) | преди 5 години |
| low_context_sensitivity.md | b7df523dc8 Fix cross-file links in non-proposal files (#1010) | преди 4 години |
| one_way.md | b7df523dc8 Fix cross-file links in non-proposal files (#1010) | преди 4 години |
| safety_strategy.md | 24b763c7e8 Fix or remove invalid anchor links, adding pre-commit (#997) | преди 4 години |
| static_open_extension.md | 00a178769f Principle: One static open extension mechanism (#998) | преди 4 години |
| success_criteria.md | 79a9b51d07 Update pre-commits, add and address flake8 (#195) | преди 5 години |
Some language goals 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.