Is it possible to implement a side table with one strong and one weak reference?

The side table in ARC is used to store weak and unowned references to avoid strong reference cycles and memory leaks.

If an object has one strong reference and one unowned reference, the side table can be implemented because the unowned reference does not increase the reference count and does not keep the object in memory.

Thus, having one strong and one unowned reference is possible and does not prevent the implementation of the side table, as unowned references are stored in the side table, while strong references are stored directly in the object.

This allows for efficient memory management, preventing retain cycles.