You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Potential for collaboration on Cross-Language Garbage Collection #2591
I am not sure if you have the same issues that JPype does with irresolvable reference loops between Java and Python. I am trying to come up with a general solution to the issue and am looking for any interested parties. If successful any language with gc can be seamlessly integrated such that users don't need to concern themselves with work arounds like weak referencing.
Sorry for the late response. This all looks very well thought through and I will try to look through Thrameos/cpython#2 to see whether we could use it as is here.
Sounds good. I look forward to feedback. I have been studying other garbage collectors and I believe that this can be generalized to Java G1, C# and a few others (At least the AI felt there was sufficient traverse functions and the momentary separation point).
My conclusion is that there can be no more than one uncooperative GC in any system, but if we can make multiple GC cooperative we can extend to many garbage collectors both locally and in distributed systems. For the Python bridges if Python is cooperative then we can extend to Java, C#, and Javascript. This applies both to direct bridges and indirect ones like Py4J.
Activity
filmor commentedon Jul 28, 2025
Sorry for the late response. This all looks very well thought through and I will try to look through Thrameos/cpython#2 to see whether we could use it as is here.
Thrameos commentedon Jul 28, 2025