Skip to content

Commit

Permalink
Change "(Optional)" to "(Recommended)"
Browse files Browse the repository at this point in the history
More polishing for promises-aplus#240: implementations SHOULD (not MAY) optimize the case
when x is known to be a promise, per discussion with @bergus.
  • Loading branch information
donhatch committed Oct 28, 2016
1 parent 658d9bb commit 449cedb
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ This treatment of thenables allows promise implementations to interoperate, as l
To run `[[Resolve]](promise, x)`, perform the following steps:

1. If `promise` and `x` refer to the same object, reject `promise` with a `TypeError` as the reason.
1. (Optional) If `x` is known to be a promise, adopt its state [[3.4](#notes)]:
1. (Recommended) If `x` is known to be a promise, adopt its state [[3.4](#notes)]:
1. If `x` is pending, `promise` must remain pending until `x` is fulfilled or rejected.
1. If/when `x` is fulfilled, fulfill `promise` with the same value.
1. If/when `x` is rejected, reject `promise` with the same reason.
Expand Down

0 comments on commit 449cedb

Please sign in to comment.