> It's the opposite, because for defer you need to be proactive and do it every time, but destructors are going to do the right thing and work
No, it's the opposite, because with defer you always see all the operations that are happening, while with destructors you have to be proactive and every time check what operations are done in your methods.
Look, I've used destructors a lot for many, many years (and still do, as it's not always up to me), they have pros and cons, some people really like them, some don't, and it's okay. It's not like there's some universal truth here or empirical data that strongly favours one side over the other.
> You might want to try it out, it would probably help with all these misunderstandings.
Thank you for your suggestion, but being one of the most foundational pieces of C++ software in the world, I think we've got it covered.
No, it's the opposite, because with defer you always see all the operations that are happening, while with destructors you have to be proactive and every time check what operations are done in your methods.
Look, I've used destructors a lot for many, many years (and still do, as it's not always up to me), they have pros and cons, some people really like them, some don't, and it's okay. It's not like there's some universal truth here or empirical data that strongly favours one side over the other.
> You might want to try it out, it would probably help with all these misunderstandings.
Thank you for your suggestion, but being one of the most foundational pieces of C++ software in the world, I think we've got it covered.