Matching unit leak?

[Hugget Sukker]

I was wondering if MatchingUnit leaks? If I convert this trigger...

• Events
• Conditions
  • Condition - If UnitGroup((UnitsInUnitGroup(Mob)) matching condition(MatchingUnit)is Alive)Equal to True))is empty Equal to True
• Actions

...into JASS, I can see that the closest resemblance I can find to MatchingUnit is something called filterUnit.
I was then wondering: should I call a function that destroys filterUnit after it has been used and AFTER "return True" has happened in the function?

I tried to destroy filterUnit just to see what would happen, but it seems that I don't know which function to call in order to remove a unit.
I know how to destroy a group, but not a single unit, so...

Questions:
1) Does MatchingUnit leak?
2) If so, how do I fix it? By destroying filterUnit... or how?
3) Even if I don't need it NOW, what do I call to destroy a single unit?

I hope that my doubts stand clear.

 

[M4stah]

Units do never leak. Unit groups do leak, but not in conditions I think

 

[Hugget Sukker]

Well. Ok. But I was corrected by someone else for using unitgroups in conditions without destroying them. To be sure I'll just use - set bj_wantDestroyGroup = true
..or what it is called.

 

[bigapple90]

thats for actually creating the group. if u dont variable the group and destroy it yourself, u can use set bj_wantDestroyGroup = true and it will destroy it for u. easier i think too ;p

 

[Element of Water]

Unit groups leak, conditions or not. FilterUnit() (Matching Unit) won't leak, however, so you should probably just Put that condition in an if-then-else in the actions and do the bj_wantDestroyGroup = true or set it to a variable and destroy it after or whatever.