W3bbo said:

koistya said:

*snip*

That's not the same thing, that's "properties for properties" which is just messed up in my opinion.

 

I'm perfectly happy with C# 2.0, I only rarely use C# 3.0 (and when I do, it's for Linq).

 

Wait a sec... this isn't an official blog posting, you're not an employee or someone involved in the language design process. Is this just an example you're proposing or what?

W3bbo, I am trying to make people think and be creative imagining the feature with me

Property extensions in C# 5.0

// A product type in this sample has a property Name of type String
var product = new Product();

// This will print "Product.Name.IsDirty: False"
Console.WriteLine("Product.Name.IsDurty: {0}", product.Name.IsDirty);

// Now let's try to update product's Name property
product.Name = "C# 4.0 in a Nutshell";

// And now this will print "Product.Name.IsDirty: True"
Console.WriteLine("Product.Name.IsDurty: {0}", product.Name.IsDirty);

// Then when you try to save this product in database, it will be easier for
// Store Repository detect which fields must be saved and which can be skipped
storeRepository.Add(product);
storeRepository.SubmitChanges();