-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Clarify JS code inlining capabilities #4701
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
Conversation
This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Hi! @lppedd |
@lppedd thank you so much for the clarification 🙏 |
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.
Nice updates! I left a couple of comments about writing and style. Could you please address them? Thank you in advance!
@AlejandraPedroza all done. Thanks! |
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.
LGTM 🚀 Thanks for your contributions!
1b89739
to
bfc9150
Compare
From time to time K/JS users make the wrong assumption that the
js()
function is able to accept any JS code.However, the truth is the K/JS compiler uses a modified version of the ES3-compliant Rhino library (1.5R3).
This PR clarifies this point, without being explicit about the version of EcmaScript that is supported.