c# - Does the CLR garbage collection methodology mean it's safe to throw circular object references around? -


I have a theory that CLR garbage collection system means that I can remove circular references by making deadlocks without goals in my object hierarchy. Is it a safe assumption for tidown and garbage collection? (Target language VB.NET)

.net waste collector is a generation mark and broom collector. If it does not use reference count then yes, it is safe for circular references. Language is irrelevant


Comments

Popular posts from this blog

.net - C# List<T>.Find(x=>x.Rectangle.Contains(Point)) FAIL -

iphone - Smoothing a rounded stroke in Core Graphics -

c++ - QtQuick: QQmlApplicationEngine failed to load component qrc:/main.qml:23 Invalid attached object assignment -