Revert spec change #91
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I don't feel strongly about this. I've heard from one person that it's important to only link to the formalized spec until our draft gets approved. On the other hand I think our draft is far more helpful to developers than the google doc. Happy to go either way here, I suppose I have a personal preference for leaving the link to our draft -- as long as that isn't directly against and TC39 rules. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We changed the linked spec from the google doc to the current draft but received feedback we should revert for now. Between the change and the revert we combine the repositories so the revert got a bit messy. This reverts to the original link to the google doc as the spec.