Yes. duck takes ownership of the vector by moving it into its internal storage.
replyAs a bonus, if you tried passing in an lvalue, it will reject the input unless you add the "copyable" trait, so it ends up mitigating some hidden copies.
Well, you’ve certainly convinced me to read your library.
replyThanks for the blog post.
No problem! Hope you enjoy :)
replyIs there another option? Or were you asking if it leaks memory?
replyMaybe you were asking if it implements custom destructors? GC?
> Or were you asking if it leaks memory?
replyyeah,
If variable c where of type void* instead of duck<Container>, the assignment on line 13 would leak the memory used by the vector<int>.