@RobertHarvey unicornvana...no.. that sounds terrible. Probably some nightmarish state you enter after reaching 50k on MSO; suddenly everyone you meet appears to have a horn sticking out of their head; at 100k it probably takes over reality completely and you find yourself in a reality where everyone is a full blown unicorn and every 3rd object is a rainbow...*shutter*

Exactly as you described, except it happens at 10K.

@RobertHarvey if that happens so help me god I will drop every damn cent of rep I have in bounties on @Ampt.

@MichaelT Great, so we can bring MSO to everywhere? No thanks, even delete votes on license questions aren't worth that 12th level of hell you describe.

@MichaelT Had no idea you were so handsome.

Yikes...

public class Customer {
private final FirstName firstName;
private final FamilyName familyName;
private final Age age;
private final Height height;

public Customer(FirstName firstName, FamilyName familyName, Age age, Height height) {
this.familyName = familyName;
this.firstName = firstName;
this.age = age;
this.height = height;
}
}

The only purpose of this is to provide a mechanism to intellisense the fields in a constructor.

But it's seriously overtaking the plumbing. Think of how you'd have to actually call the constructor. You'd have to new up a copy of each parameter object.

So now it

= new customer(new FirstName("Tom"), new FamilyName("Smith")

Ick.

You might as well do this:

= new Customer(new { FirstName = "Tom", FamilyName = "Smith" });

and use Reflection to get all the parameters, like they do in ASP.NET MVC. Except, of course, that it won't intellisense.

If you're willing to forego the Constructor...

= new Customer() { FirstName = "Tom", FamilyName = "Smith" }

Which will intellisense, but won't give you constructor verification.

@RobertHarvey That's terrible. First names are constructed with a not type-safe enough string. You need a MyString class for that.

Honestly, I don't really get the concept. See here, but I don't feel like it is fully baked:

darrenhobbs.com/2007/04/11/tiny-types

@psr No; FirstName should take a NameString (otherwise it could get non-name parameters, like a shopping list string or maybe a hard-coded SQL string) ...though obviously NameString is a subclass of MyString to ensure strings from other libraries don't get in there, that could be dangerous.

It's turtles all the way down...