Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

如何阅读一份提案草案？ #8627

Merged
merged 2 commits into from
May 23, 2021
Merged

如何阅读一份提案草案？ #8627

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9aa0daf
translation done
PassionPenguin May 20, 2021
d4dca39
Apply suggestions from code review
PassionPenguin May 22, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions article/ECMA-TC39/Reading-a-proposal-draft.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,18 +2,18 @@
> * 原文作者：[Ecma TC39](https://github.com/tc39/how-we-work)
> * 译文出自：[掘金翻译计划](https://github.com/xitu/gold-miner)
> * 本文永久链接：[https://github.com/xitu/gold-miner/blob/master/article/ECMA-TC39/Reading-a-proposal-draft.md](https://github.com/xitu/gold-miner/blob/master/article/ECMA-TC39/Reading-a-proposal-draft.md)
> * 译者：
> * 译者：[霜羽 Hoarfroster](https://github.com/PassionPenguin)
> * 校对者：
PassionPenguin marked this conversation as resolved.
Show resolved Hide resolved

# Reading a proposal draft
# 阅读一份提案草案
PassionPenguin marked this conversation as resolved.
Show resolved Hide resolved

Each proposal which is Stage 2 or higher has a specification text draft, located at `https://tc39.es/proposal-<name>`. This is the authoritative definition which implementations should use as a reference; README text or issues may be used for context.
每个处于第二阶段或更高阶段的提案都有一个规范文本草案存储在 `https://tc39.es/proposal-<name>`。这些草案都是供实现该功能参考的权威性的定义；README 文本或 Issue 可能会在它们的上下文中引用这份草案。
PassionPenguin marked this conversation as resolved.
Show resolved Hide resolved

The specification text for proposals is phrased as a diff over the [current draft specification](https://tc39.es/ecma262), possibly with the addition of certain other proposals. When an entirely new section is added, it is not highlighted, but when existing sections are modified, they are highlighted in green for insertions and red for deletions.
提案规范文本的表达可能会与[当前规范的草案](https://tc39.es/ecma262)有所不同，也可能会对某些其他提案有所添加。当添加一个全新的节时，它不会突出显示，但是当修改现有节时，它们会以绿色突出显示，强调是插入的内容，而红色的标识则表示删除。
PassionPenguin marked this conversation as resolved.
Show resolved Hide resolved

Specification text is meant to be interpreted abstractly. Only the *observable semantics*, that is, the behavior when JavaScript code is executed, need to match the specification. Implementations can use any strategy they want to make that happen, including using different algorithms that reach the same result.
规范文本旨在被抽象地解释（译者注：即，只对实现的运行效果有所要求，而在如何实现上没有规定）。只有*“可观察到的语义”*，即执行 JavaScript 代码时的行为表现，才需要与规范匹配。实现可以使用他们想要实现的任何策略，包括使用达到相同结果的不同算法。
PassionPenguin marked this conversation as resolved.
Show resolved Hide resolved

For more details on reading specification text, see Timothy Gu's [How to Read the ECMAScript Specification](https://timothygu.me/es-howto/) and the ECMAScript specification's [Notational Conventions](https://tc39.es/ecma262/#sec-notational-conventions) section.
想要查看更多有关如何阅读一份规范文本的详细信息？请参考 Timothy Gu 的[如何阅读 ECMAScript 规范](https://timothygu.me/es-howto/) 一文和 ECMAScript 规范一文中的[标志性公约](https://tc39.es/ecma262/#sec-notational-conventions)章节部分内容。


> 如果发现译文存在错误或其他需要改进的地方，欢迎到 [掘金翻译计划](https://github.com/xitu/gold-miner) 对译文进行修改并 PR，也可获得相应奖励积分。文章开头的 **本文永久链接** 即为本文在 GitHub 上的 MarkDown 链接。
Expand Down