14:26 <fangerer> antocuni: Sorry for the late answer. Concerning the reason why the per-module debug mode is not for free on GraalPython: In terms of run-time performance, there is just a small penalty because there are two different (Java) classes for the contexts and we need to dispatch between them.

14:26 <fangerer> But that's not my main concern. My concern is more about that it makes implementation more complicated for us.

14:28 <fangerer> Mainly because we intrinsified the debug context (and all its functions).

15:14 <antocuni> what do you mean by "intrinsified"?

16:23 <fangerer> We've implemented them in our host language (i.e. Java). We don't use the C implementation of the debug context functions.

16:30 <antocuni> ah, I see

16:30 <antocuni> well, I suppose that we can say that PyPy and CPython supports per-module debug and GraalPython doesn't

18:27 <Hodgestar> fangerer: It feels like making the code nice for per-module debug mode on the GraalPython side is a solvable problem. You already have the code for debug mode, so it's just about structuring things nicely and using the code in the right place? Obviously you know a lot more about GraalPython internals than me -- I'm just saying that it feels like there should be a nice way to do it?