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

Discuss desired breaking Java API changes for v2.0.0 #1059

Open
p-bakker opened this issue Oct 14, 2021 · 1 comment
Open

Discuss desired breaking Java API changes for v2.0.0 #1059

p-bakker opened this issue Oct 14, 2021 · 1 comment
Labels

Comments

@p-bakker
Copy link
Collaborator

As per , the idea is to schedule desired/required breaking api changes for v2.0.0

Besides required API needed to make Rhino compliant to the EcmaScript spec, there has been word in the past that some breaking API changes might have to be made in order to:

  • make Rhino more maintainable
  • make Rhino more performant
    However, what those desired breaking API changes are have not been specified.

Hence this case to get claritiy on those.

Some pointers mentioning this: #734 (comment) & #734 (comment)

@p-bakker
Copy link
Collaborator Author

Maybe not so much a potential breaking change, but in #268 (comment) the suggestion was made to improve the mechanism of getting the ids of a Scriptable by something that doesnt depend on copying arrays all the time, like an iterator

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

No branches or pull requests

1 participant