I think there is still a bug here. Can you change your tests so that you
construct the DTree on the heap with the 'new' operator? Then after you make
the copy with the copy constructor, delete the first DTree. After that, check
the values of the copied DTree. This will ensure that we are not using memory
that the first DTree allocated, and that we have a safe copy. Let me know if I
can explain this further.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/mlpack/mlpack/pull/824#issuecomment-266483681
_______________________________________________
mlpack mailing list
[email protected]
http://knife.lugatgt.org/cgi-bin/mailman/listinfo/mlpack
