this post was submitted on 13 May 2024
4 points (61.1% liked)
C++
1761 readers
1 users here now
The center for all discussion and news regarding C++.
Rules
- Respect instance rules.
- Don't be a jerk.
- Please keep all posts related to C++.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
And even the presented fix hurts my eyes. Should have used a
unique_ptr
oroptional
.Exactly, raw pointers are very rarely the way to go
You'd be missing the whole point too if you think that the pointer is the root cause. The problem is that the class is not designed to be copy-able, let alone moveable. Your suggestion to use a
unique_ptr
will also blow up in your face the moment you try to copy an instance.Depends on what semantic you want. Sure, if you use a
unique_ptr
member, you will get a deleted copy constructor/operator - I wouldn't consider that blowing up in my face.