Unique give false safity guaranties.
- Assignment of
RefCounted!Tshould be prohibited.
RefCounted!Tcan keep the allocator of the previous object that doesn't match the allocator used to create the new one. Only
RefCounted!Tcan be assigned to
- The constructor that takes an existing object and the allocator should be
@system. There is no guarantie that the object was really allocated with the given allocator.
refCountedwhich constructs the object and wraps it into
RefCountedcan be trusted.
unionsthe constructor and destructor can only be trusted if the appropriate methods of the
Uniqueshould know of each other.
Uniquecan be assigned to
RefCountedtakes over the ownership of the object. The assignment can be trusted since
RefCountedcan take the information about destroying the object from
- Similar rules apply to
No data to display