wlav

As said above, the Python side isn't the problem, so that's not where the fix can be, it's on the C++ side. As such, I really don't think any of...

Yes, you can use Cling w/o cppyy to get the same features, but yes, the marshaling is then yours to do (of course that's true now as well from Python,...

For the first, using cppyy is just a convenience (if not hack), to allow you in essence to `pip install` cling as brought in by `cppyy`. You should NOT close...

Pinging @aaronj0 here, in case he has a cmake fragment to embed clang-repl? Yes, building LLVM can take a significant amount of time; recommend to always to a full parallel...

@vgvassilev do you have an example code of the most basic Cling setup?

Looks like upstream has created an API for this use case: https://github.com/compiler-research/CppInterOp/pull/607 (I've not yet tested it; just adding it here for reference.)

What does "work out of the box" mean? `assert()` is a macro, not a function that can be bound/called from Python. For the C++ side, you can check with `cppyy.cppexec("std::cerr

Found it ... it's hard-wired in cling's `CIFactory.cpp`: ``` // cling wants to JIT O1 by default. Might want to revisit once we have // debug symbols. PPOpts.addMacroDef("NDEBUG=1"); ``` I...

Per upstream, Clang's behavior is to enable `NDEBUG` if optimization level is greater than 0. Pre-compiled headers/modules should not be mixed with interpreter code where `NDEBUG` differs, as there could...

I forget whether this is intentional ... There have, over time, been different opinions on how to deal with C++ exceptions from methods and how they fit into overloads. The...