Earlier quoted context omitted.
Well, GC has indeterminate timing in and of itself . Reference counting does not. It can still trigger indeterminate timing if the destructor calls free, or if the "thing" going out of scope is a pointer, but that's on the destructor or the pointer, not on reference counting per se.
> but that's on the destructor or the pointer, not on reference counting per se. It is on reference counting per se. If the reference count of a reference goes to zero, the runtime has to make the memory available for reuse. That’s what I called ‘calling free’. Also, about “GC has indeterminate timing in and of itself”. Again: define what you mean by it. Yes, The timing of allocating an object can vary depending on t…
And then whether you blame that on reference counting or garbage collection or heap allocation is kind of an arbitrary distinction.
OK, I get it. You were right :-)