Hashtable Leak?

[MeKC]

local unit u = CreateUnit(Player(0),'hfoo',0,0,0)
call SaveUnitHandle(udg_hashtable,1,1,u)
set u = null

In this code, we created a local variable to store the unit into the hashtable.
And after that we had to null the local variable.

What about this script below. Now we did not created any local variables.
But will this leak in some way?

call SaveUnitHandle(udg_hashtable,1,1,CreateUnit(Player(0),'hfoo',0,0,0))

 

[Reaper2008]

No. Generally, the native CreateUnit, and all (i think) others do not leak.

 

[MeKC]

So this will be faster, since you avoid to create and null a local variable?

call SaveUnitHandle(udg_hashtable,1,1,CreateUnit(Player(0),'hfoo',0,0,0))

 

[Dr Super Good]

Yes, it is faster. However remember to clear it from the hash table when no longer needed or the index will not get recycled and the hashtable will have an index blocked permantly. (hashtables use arrays of fixed size which results in them slowing down when full I believe).

Luckilly there are like 3 natives you can use to remove handles from hashtables, those are flush a specific location, flush a parent and flush the whole damn thing. Highly convenient hehe. . .