Rhino wish list
The following are some ideas of ways people can contribute to Rhino. If something below strikes your fancy, write to norrisboyd (at) gmail (dot) com.
Being able to change the internal
For more information see this bug I submitted.
This is underway, see the tracking bug.
Rhino's regexp engine was developed before Java had support for regular expressions. It would be good to replace Rhino's implementation with Java's implementation which we hope will be faster and more correct.
First we need to look at the differences between the Java and ECMAScript regexp grammars. If they are identical, we can substitute easily. If they are different, we need to understand the differences and come up with a design for detecting and handling the ECMAScript-specific cases. Then we need to replace the Rhino implementation with calls to the Java implementation. See Bug 390659
Remove uses of old Java collections (Vector, etc.) and replace with modern equivalents. Take care not to compromise thread safety.
Analyze benchmarks and see how Rhino can improve performance.
Probably the best starting point is the V8 benchmarks.
Provide APIs to access the AST of parsed scripts. Done