Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider using unique_ptr or shared_ptr instead of raw pointer access #16

Open
samhatchett opened this issue Aug 4, 2016 · 0 comments

Comments

@samhatchett
Copy link
Member

For owned or transferred pointers, we should be using std::unique_ptr for RAII and memory management. Especially in context of exception handling and potentially returning new allocations to client code which may not assign and own the pointer. For example, all factory methods leak by default.

@samhatchett samhatchett changed the title Consider using unique_ptr or shared_ptr instead of raw pointer access Consider using unique_ptr or shared_ptr instead of raw pointer access Aug 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant