Well you can always switch it off and see what happens, "complex real world example" or not. You can also disable it selectively per thread or per time critical code part. you can also break up cycles manually via `ptr` and that's where Nim should be improving. Swift too embraces this model.
- Re: Nim GC Performance Araq
- Re: Nim GC Performance jlp765
- Re: Nim GC Performance Varriount
- Re: Nim GC Performance jlp765
- Re: Nim GC Performance Varriount
- Re: Nim GC Performance Varriount
- Re: Nim GC Performance Stefan_Salewski
- Re: Nim GC Performance dom96
- Re: Nim GC Performance zolern
- Re: Nim GC Performance Varriount
- Re: Nim GC Performance Araq
- Re: Nim GC Performance Stefan_Salewski
- Re: Nim GC Performance dom96
- Re: Nim GC Performance JohnS
- Re: Nim GC Performance dom96
- Re: Nim GC Performance evacchi