-
Notifications
You must be signed in to change notification settings - Fork 13
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
New definitions of "H", "P", "p" and "∞", supposed new Features ASYNC_FUNCTION
, ITERATOR
and JAPANESE_INFINITY
#46
Conversation
just added "p" definition. |
Currently, it's not trivial to add a new feature, I'll see if I can write some instructions. We need the features before we can add the new definitions. |
when will the instructions be finished? how will it be delivered? |
I should be able do it in the next days, I would like to include links to some example commits for reference. Maybe this should be a markdown page in the repo or a wiki page, what do you think? |
I think wiki page is better. And, those existing Markdown pages for API and features can be also turned into wiki pages too. |
sorry. I found that wiki was built days before but only have generic contribution guideline. when will you have specific instruction about creating new features? |
I'm working on this. |
I've added feature |
mostly clear, but IDK how empty function can be used as simulation of |
ITERATOR
and JAPANESE_INFINITY
ASYNC_FUNCTION
, ITERATOR
and JAPANESE_INFINITY
btw, I just added a new definition of "P" for Node.js 7.6-15, which relies on a new feature: |
ASYNC_FUNCTION
, ITERATOR
and JAPANESE_INFINITY
ASYNC_FUNCTION
, ITERATOR
and JAPANESE_INFINITY
That's fine. The emulated objects are just for testing, they are not expected to conform to the specification. For
You could have a look at how
It's necessary to overwrite the |
Co-authored-by: Francesco Trotta <[email protected]>
For simulation of |
Feel free 👍 |
Co-authored-by: Francesco Trotta <[email protected]>
Co-authored-by: Francesco Trotta <[email protected]>
Co-authored-by: Francesco Trotta <[email protected]>
Co-authored-by: Francesco Trotta <[email protected]>
sorry, but that's the best I can do. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! That's not bad all 👍I found some time to review this yesterday and left some suggestions.
Co-authored-by: Francesco Trotta <[email protected]>
Co-authored-by: Francesco Trotta <[email protected]>
Co-authored-by: Francesco Trotta <[email protected]>
Co-authored-by: Francesco Trotta <[email protected]>
Co-authored-by: Francesco Trotta <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almost there.
Co-authored-by: Francesco Trotta <[email protected]>
Co-authored-by: Francesco Trotta <[email protected]>
Still anything to do? or can be merged now? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, was just testing browser compatibility. Left some comments.
Co-authored-by: Francesco Trotta <[email protected]>
Co-authored-by: Francesco Trotta <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! LGTM.
idk how hard adding new features by myself is, but I have some new definitions which rely on introducing new features (
ITERATOR
andJAPANESE_INFINITY
).ITERATOR
is for new browsers which have iterator methods, andJAPANESE_INFINITY
is for wider usage ofInfinity.toLocaleString()
in getting "∞" (IE11 on win7 Japanese Infinity string is "+∞").