List and Enumerable do very similar things. Consolidate them?

[rubberduck203]

Do we need both Enumerable and List? Should we consolidate functionality, or simply refactor them so that one calls the other to remove code duplication?

[ptwales]

I say push the most primitive functionality's from Enumerable to List and have Enumerable be a pseudo Sub Class of either List or TypedList, since Enumerable is immutable and List isn't.
Enumerable should be the most commonly used class though. List should just be for sub-classing.

[rubberduck203]

@ptwales what did you have in mind when you say "primitive functionality"? We should come up with a list of methods to move.

[ptwales]

I'm thinking:

• ToArray
• Create
• CreateFrom
• Replace Append(variant) with Add(ParamArray)
• First
• Last

And maybe renameFirst with Head and create Tail and Init. But those might make more sense in an immutable class.