Feature Request: List:Copy or copy constructor

[tullisar]

I'm curious if there'd be any value in the List class having some copy utility? Sometimes I'd rather retain a copy of data (when it won't impact performance) than retain a reference to a list that may have been passed in as a function argument. I have some quick and dirty boilerplate that I use (admittedly only in 2 places ha), but thought the library might benefit from built-in support.

[Mayron]

Hey @tullisar. The other feature request requires most of the framework to be implemented and it's been a difficult challenge. Sadly, I've had a lot going on IRL but I haven't stopped. I'll most likely be able to pick both issues up in April.

I think the collection classes could be greatly improved. I moved them into their own package Pkg-Collections and want to at least make two versions of each class, one for a Generic version of each and the standard versions as they are now. I've not put into practice most of the methods for each. The Pkg-Collections package should be optional so you can make your own List class if required.