<@U3SK5B492> How expensive is attaching and detach...
# kotlin-natives
spierce7
10/23/2018, 3:17 AM@olonho How expensive is attaching and detaching an object from a thread? If I have a List with 100,000 items, should I worry about performance for attaching and detaching objects from a thread?
o
olonho
10/23/2018, 3:25 AMcurrently, it’s
O(subgraph_size)s
spierce7
10/23/2018, 3:45 AMthx
k
kpgalligan
10/23/2018, 8:27 PMSort of related (but only because of detached object graphs). If something in your detached graph references something outside of your detached graph, does the reference count decrement when you detach, and if not, if you never attach again, is that memory effectively leaked? Was playing around with state and that thought popped into my head.
o
olonho
10/23/2018, 8:46 PMThe only case it could happen is for frozen objects, and yes, such objects will be leaked
k
kpgalligan
10/23/2018, 8:48 PMI was just playing with some state and thought I was capturing unfrozen state, but I was probably freezing it unintentionally
kpgalligan
10/23/2018, 8:49 PMYeah, I guess you’d have bigger problems detaching unfrozen state. Had a red eye flight and didn’t sleep. Slow brain
o
olonho
10/24/2018, 9:07 AMwell, there’s no problem detaching frozen/permanent state, we can just consider those being “outer” to detached graph and shareable by default, so they not block detaching
k
kpgalligan
10/24/2018, 9:08 AMRight. Just saying trying to detach non-frozen state is obviously a bad plan
kpgalligan
10/24/2018, 9:08 AMI mean references to
2 Views