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.

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

Create a "Differences from Promises/A" section or secondary document. #17

Closed
domenic opened this issue Nov 2, 2012 · 3 comments
Closed

Comments

@domenic
Copy link
Member

domenic commented Nov 2, 2012

This might allow us to delete a sentence or two in the introduction, and helps highlight what the wins of this spec are. Here's what I remember so far:

  • No progress handler (leave it for future spec work).
  • No "interactive promise" stuff.
  • Cover the case of handlers returning a promise
  • Update/clarify terminology: "fulfilled", "rejected", "reason", and "pending" instead of vague words like "completion," "failure", "finished", "failed state".
  • Specify that the rejection reason passed to onRejected is the thrown error.
  • Require asynchronous resolution.
  • Specify ordering of callbacks for subsequent calls to then.
  • Do not require promise1 !== promise2.

This might be best put in a second document in the repository (differences-from-promises-a.md) which could allow us to expand on each item, and avoids crowding the main spec with stuff of mainly-historical interest.

@briancavalier
Copy link
Member

+1 on separating this info, either in a separate section (at the bottom), or a separate doc. If it's a separate doc, we could just link to it from the spec.

@briancavalier
Copy link
Member

Seems like a section at the bottom of the spec would work, and we can link to from somewhere in the first few paragraphs. I can try to put that together later tonight. If people prefer a separate doc, we can always move it easily.

@domenic
Copy link
Member Author

domenic commented Nov 6, 2012

I would prefer a separate doc. I think non-normative and especially historical stuff should be kept out of the spec proper.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants