I know |AEManagedValue setValue| is documented as having to be called on the main thread, but I mistakenly called it on a GCD background thread.
...it turns out that if you do that, AEManagedValue pollTimer doesn't work, and so old values never get released.
It would be nice for users if |AEManagedValue setValue| checked that it was on the main thread. You could limit the check to when poolTimer is created, to minimize runtime overhead.
I know |AEManagedValue setValue| is documented as having to be called on the main thread, but I mistakenly called it on a GCD background thread.
...it turns out that if you do that, AEManagedValue pollTimer doesn't work, and so old values never get released.
It would be nice for users if |AEManagedValue setValue| checked that it was on the main thread. You could limit the check to when poolTimer is created, to minimize runtime overhead.