Implement Weak References for Breaking Cycles

Breaking Cycles with Weak Refs

Strong refs keep objects alive; weak refs observe without retaining. Java WeakReference and Swift weak let caches and parent pointers avoid cycles. When only weak refs remain, object is collectable.

Weak Reference Semantics

Weak ref field does not increment refcount or mark bit. On collection, weak refs null out. Finalizers run once after weak resolution in some runtimes.

c
Loading…

Phantom vs weak vs soft refs differ in finalization timing
Weak tables need ephemeron semantics in GC
JNI global refs are strong; weak global for caches
Cycle: A<->B needs one weak edge to break

Connecting to real compilers

Production compilers embed this step inside a longer pipeline. GCC flows through cpp, cc1, assembly, and ld; Clang uses the driver, Sema, LLVM IR passes, and a target backend. LLVM bitcode, JVM bytecode, and WASM are other familiar IRs at the same layer. The exercise isolates one pass so you can test it alone before chaining it to the next stage.

Why for this exercise

You will implement weak references for breaking reference cycles. This exercise asks you to track weak slots separately from strong roots so objects are collected when only weakly reachable.

Implement weak references in C with a simulated garbage collector.

Requirements:

Define GCObject with strong_ref_count and a weak_ref_list
Define WeakRef structure with target pointer and a "living" flag
Implement gc_create_object() that allocates and registers with GC
Implement strong_retain() and strong_release() for reference counting
Implement weak_ref_create() that creates a weak reference (does not increment count)
Implement weak_ref_deref() that returns target if still alive, NULL if collected
When strong_ref_count reaches zero, free object and invalidate all weak refs
Demonstrate a reference cycle broken by weak refs
Print object lifecycle and weak ref state transitions

Test:

Show strong ref counting
Show weak ref creation and deref
Show cycle broken by weak refs
Show weak ref invalidated after target freed

Breaking Cycles with Weak Refs

Weak Reference Semantics

Weak ref field does not increment refcount or mark bit. On collection, weak refs null out. Finalizers run once after weak resolution in some runtimes.

c
Loading…

Phantom vs weak vs soft refs differ in finalization timing
Weak tables need ephemeron semantics in GC
JNI global refs are strong; weak global for caches
Cycle: A<->B needs one weak edge to break

Connecting to real compilers

Why for this exercise

You will implement weak references for breaking reference cycles. This exercise asks you to track weak slots separately from strong roots so objects are collected when only weakly reachable.

Implement weak references in C with a simulated garbage collector.

Requirements:

Define GCObject with strong_ref_count and a weak_ref_list
Define WeakRef structure with target pointer and a "living" flag
Implement gc_create_object() that allocates and registers with GC
Implement strong_retain() and strong_release() for reference counting
Implement weak_ref_create() that creates a weak reference (does not increment count)
Implement weak_ref_deref() that returns target if still alive, NULL if collected
When strong_ref_count reaches zero, free object and invalidate all weak refs
Demonstrate a reference cycle broken by weak refs
Print object lifecycle and weak ref state transitions

Test:

Show strong ref counting
Show weak ref creation and deref
Show cycle broken by weak refs
Show weak ref invalidated after target freed

Topic Overview

Breaking Cycles with Weak Refs

Weak Reference Semantics

Connecting to real compilers

Why for this exercise

Implementation Task

Progressive Hints

Resources

Open Source

Implement Weak References for Breaking Cycles

Topic Overview

Breaking Cycles with Weak Refs

Weak Reference Semantics

Connecting to real compilers

Why for this exercise

Implementation Task

Progressive Hints

Resources

Open Source