Is there a better way to shallow-clone a generic List<> than create a new List<> with the old list as the constructor's argument
List<Foo> list1 = new List<Foo>();
// Add a zillion references to list1
List<Foo> list1Copy = new List<Foo>(list1);
The generic lists don't seem to provide the Clone() method. Creating a custom, inheirted List<> is something I'd like to avoid.
Cloning Generic list?
Hot Topic
- Exception: DataTable internal index is corrupted: '5'. on ...
- Parsing data from MSQL to TextBox
- Help getting started on serial comms
- SQL Server 2005 XML type looses spaces
- Using TableAdapter for thousands of rows
- xmldocument class
- Parameters in a sql statement
- Advantages of the BackgroundWorker Class
- Howto: Validating Data on Form Gracefully?
- GAC Assembly is There, But Where's the DLL?
.NET Development
- Multiple FTP commands via one connection
- The credentials supplied to the package were not recognized
- Internet connection
- Server based certificates
- Solution
- Socket BeginAccept Method Memory Leak?
- Compile Typed Dataset
- DirectorySecurity.GetAccessControl method failing
- Remote proxy has no channel sink
- Problem with .NET 2005
Cloning Generic list?
FSOL
//Add some references
List<Foo> mylist_with_cloned_members =
new List<Foo>( (Foo[])mylist.ToArray().Clone() );
Thomas Thayil
Sushil Chordia
Implement Icloneable interface in Foo Class.
List
<Foo> cloneFoos = new List<Foo>(); foreach(Foo f in Foos){cloneFoos .Add((
Foo)f.Clone());}
clark121121
I don't think I understand why you want to avoid
List<foo> list1Copy = new List<foo>(list1);
What would Clone() provide that this technique does not
-Tom Meschter
Software Dev, Visual C# IDE