I can't do this either :(( const DateTime tick = new DateTime(2001, 1, 1);

- Pete

True enough. I'd love to banish usings somehow. I want to use a create & use an class, not manage it's lifetime.

- Pete

With C# getting to version 7+ I wish I could have some basic improvments. Is it me or do you get confused by this? Why can't I say

const DateTime today = DateTime.Now;

I can see readonly for parameters and such, but I would be happy using const there too

void Doit(const MyObj arg) ...

For properties, why can't I hide the worker variable for the rest of the class?

public int PageNbr
{
int _worker = 9;

get { return _worker;}
set { _worker = value; }
}

For destructors, why can't you give me option to destroy right away? I hate disposing with all its using code bloat. How about a free keyword on a variable or something to get me out of the business of resource management. If you open a file and a DB you have to nest usings before you even get started doing some work! Or maybe I'm missing something?

- Pete

Every user who is upgraded from an old copy of office 2010-2013 hates the new office. I get to watch accounting power users fall back to quibbling angry children as they rant about how things have changed. Then there's the occasional update we it forgets the current directory, preferences, etc... Don't even get them started on how my clicks it can take to open a file! Software by committee or demons work? -Pete

- Pete

I agree. Plus you can backup/snapshot the VM before major updates / code changes.

- Pete

I'd like to see built in threading. Example: int x = CalcXDataValues() &; <- run as thread int y = CalcYDataValues() &; int z = x + y; // will not execute until x and y are set!

- Pete