> The main limitation is that Nim =destroy and =copy hooks for object do not > get called properly by the C++ container because they're not mapped to their > C++ equivalent.
I do not yet understand the destroy/copy concept properly. The `toSeq` proc I show in the post seems to work. In what scenario would the destroy/copy issue cause a real problem? > PR welcome if you want to add std::list to the repo Yes, I can send a PR once I have mapped a good amount of that library, and also with doc-strings and tests added. I am [this same person](https://github.com/Clonkk/nim-cppstl/pull/13) hehe. > If you need more C++ STL container you can check out : > <https://github.com/Clonkk/nim-cppstl> You missed reading references section of that post! :D
