I can't remember where I first saw the AddNew() method Add(new) concept -- or, at least the concept behind it -- but I liked it. I'd really like to see the same thing added to all generic collections. For instance...
List<Person> people = new List<Person>();
Person person = people.AddNew("Michael", "Flanakin");
I admit, this doesn't save you a whole lot of typing, but it is very convenient. Essentially, I'd like every constructor to be represented by a corresponding AddNew() method. So, if I have default, id only, and a first and last name accepting constructors, I want 3 additional AddNew() methods...
public Person AddNew();
public Person AddNew(int id);
public Person AddNew(string firstName, string lastName);
As is, generics alone cannot do this with the level of integration I'd like to see, which would include reusing XML documentation already in place for the constructor. You can, however, hack something to give you this capability by using the params keyword powered by reflection in the back-end. Of course, I'd be worried about performance with an implementation like that. I don't see this being added, tho. The cost of implementing it probably wouldn't be worth the 6+ characters you'd save ("new " + name of class + "(" + ")"). Then again, perhaps this could be a mod to generics, which is already lacking, when it comes to constructor constraints.
Edit: I realized after posting this that it wasn't an AddNew() method I was looking for, but simply additional Add() methods. While this would save an additional 3 characters, the "is it worth it" argument is still there. I'd still say its convenience makes its case, tho. Maybe I'm just lazy. I changed the code samples are referred to this idea as the Add(new) concept, even tho you don't actually use the new keyword.