interpreter

Most (?) of the built in functionality currently lacks corresponding documentation. The functionality to grab and attach the docs is there, the docs just haven't been added.

This, I believe, could make a good first issue for many people, it just involves taking the documentation and adding it before (after works too but most current examples add it before) the #[py(function/method/class)] at

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

Feature
Support - that is ignore - the unix shebang, e.g. #!/usr/bin/boa
This is something nodejs and deno both do: they just ignore the unix-style shebang, and this is sometimes required to execute scripts written for either.

Example code

#!/bin/whatever
console.log("I still work");

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!

1. The rf204_extrangefit.py should be translated also to C++
2. The rf204b_extendedLikelihood_rangedFit.C tutorial should also be translated to C++
3. The [rf204b_extendedLikelihood_rangedFit.C](https://root.cern.ch/doc/master/rf204b__extendedLikelihood_

Currently, our math module isn't completely filled with necessary math functions, where you can contribute us by adding more math functions. This issue has reference on how to add log function to the math module.

How to implement

PR #154 has example on how to add log10 to the math module, which you can use as a reference to add log (base 2) function.

Finally

And don't forget