Post #2832027

The same dev who was arguing with me yesterday because of the overhead of having a basic enum (or sealed class) to cover an unknown state instead of a boolean (paired/unpaired versus unknown/paired/unpaired) despite the fact it'd make any kind of sane UI impossible is now arguing that we shouldn't null a stale reference of a very heavy mechanism to mark it for GC. I'm sure he just likes to be contrary. Is it the weekend yet?