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

In the prototype implementation of value types support, the letter Q is used as a prefix in the bytecode for the signatures of classes that are value types, as distinguished from concrete identity type classes, interfaces and abstract classes, whose signatures are prefixed with the letter L.

Minimal changes to handle the Q prefix in the JIT compiler were merged into OpenJ9 in [pull reques

Describe the bug
The following code doesn't compile:

const message = 'Hello world!';
const wrapper = { message };

Expected behavior
It should work as an equivalent of const wrapper = { message: message };

Build environment:
Boa Playground

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!

Explain what you would like to see improved

After root-project/root#7399 we can now add RNTuple field descriptions to the output of RNTupleDescriptor::PrintInfo, as in TTree::Print().

Optional: share how it could be improved

Right now I think the most appropriate info category is `kStorageDetails