Swift Pointer Syntatic Sugar

Are you suggesting T* be syntactic sugar for UnsafeMutablePointer<T>? Because your implementation displays a new operator retrieving the pointer for a value (Side note: Your implementation allocates a new pointer rather than actually point to the value passed. I don't know if that's what you were going for. This also leaves the deallocation up to the caller.)

1 Like