interpreter

See e.g. #2570. Some of the unit tests there with "wrong error message" should be somewhat easy to fix - just correct the error message we have to match CPython's. Others might be trickier, since you'll need to add diagnostics to recognize bad syntax and give a more detailed error than "unexpected token". Also, I think around half of them could be fixed just by adding "invalid syntax" in the messa

Our safe wrappers around Javascript objects are not easily identifiable by looking at the docs, as you can see from the next screenshot:

I would propose moving all implementors of the JsObjectType trait to a standalone module and point to that module in the home page of our docum

Depends on eclipse-openj9/openj9#15172

Implement IsVirtualThread

See https://download.java.net/java/early_access/jdk19/docs/specs/jni/index.html

I have an idea for a new feature for jQuery Terminal

I think that to be correct the LICENSE file should include copyright notes from all projects that are included. And a copy of all licenses is inside that file.

All libraries from at the beginning of the jquery.terminal-src.js file should be looked up and

Scenario:
I have a project, with build tools of cmake, when I try to run it with cling. It prompts some headers are not included.

So I was wondering if there is a way to make use of the cmake script to load the build environment into cling and run directly?

Appreciate the great work!

Current behavior:

root [0] TFile f("root://eospublic.cern.ch//eos/root-eos/benchmark/Run2012B_SingleMu.root")
Error in <TFile::TFile>: file /eos/root-eos/benchmark/Run2012B_SingleMu.root does not exist
(TFile &) Name: /eos/root-eos/benchmark/Run2012B_SingleMu.root Title:

Desirable behavior:

root [0] TFile f("root://eospublic.cern.ch//eos/root-eos/benchmark/Run2012B_Single

This is a config file for clang-format, a tool that is already used by many editors and adopted by many projects to format the code and ensure that the style is consistent.
It could even be used as a git hook or in the CI/CD workflow to ensure that new patches respect the coding style.
A config can derive from other preexisting configs (like Google's, LLVM's or Mozilla's) so it's not a big eff