https://github.com/graalvm/graaljs/blob/21177b89d21e8082607d688567a55f020d91626d/graal-js/src/com.oracle.js.parser/src/com/oracle/js/parser/Parser.java#L1062

I'm planning to migrate from beaver JS parser to GraalJS parser for implementing javascript grammar in the eclipse editor. But I realised it doesn't have the implementation for error recovery strategies.

For example:
Math.

If I g

As see from #53 we can have broken/dead links, links that once worked can be unavailable for reasons outside the control of this project/repo!

Hence I have decided to manually scan (for now) the repo from time to time for such links and fix them - if there is one. Here are the steps to take:

New broken/dead links

• find missing links using, markdown-link-check (see https://www.npmjs.c

From the documentation: Return the names of all the built-in objects. These are fetched directly from the symbol table of the R interpreter.

In FastR the list of builtins is accessible in the TruffleRLanguage, which is accessible via RContext.getInstance().

Add Javadoc to document the examples in TornadoVM.

This affects the packages under the examples module:

https://github.com/beehive-lab/TornadoVM/tree/master/examples/src/main/java/uk/ac/manchester/tornado/examples

When bailing out with an error, print where in source error occurred. We already set source section in ast visitor but do not print it in error cases.

Decide if early or lazy loading is better for graalphp.

• pro for eager: we may implement phpdoc semantics into parsing (types)
• however, new versions of php support type hints and dont have to rely on comments
• i think for now we lazy loa

See TODOs in ClipboardExtendedPlugin.java.