Syntactic sugar?

Question

I came across the term syntactic sugar these days when I was studying the use of await and async in C#. This question explains what syntactic sugar or syntax sugar is What is syntax sugar and how it works?.

Besides await and async, which others exist in C#?

Answer 1

It is difficult to separate exactly what is exactly sugary from what is not. It is also difficult to define all the sweets of C#, but here are some that make the code much clearer.

lock

That:

lock (_lock)
{

}

In place of:

object obj;
var temp = obj;

Monitor.Enter(temp);

try
{
    // body
}
finally
{
    Monitor.Exit(temp);
}

foreach

That:

IEnumerable<int> numeros = new int[]
{
    1, 2, 3, 4, 5
};

foreach (int i in numeros)
{

}

In place of:

var enumerator = numeros.GetEnumerator();
while (enumerator.MoveNext())
{
    int current = enumerator.Current;
}

using

That:

using (FileStream f = new FileStream(@"C:\foo\teste.txt", FileMode.Create))
{

}

In place of:

FileStream f2= new FileStream(@"C:\foo\teste.txt", FileMode.Create);
try
{

}
finally
{
    f2.Dispose();
}

Auto properties

That:

 public string Foo { get; set; }

In place of:

private string _foo;
public string Foo
{
    get { return _foo; }
    set { _foo = value; }
}

Nullable

That:

int? nullInt2 = null;

In place of:

Nullable<int> nullInt = new Nullable<int>();

Operator `??`

That:

int myNum = nullInt ?? 0;

In place of:

int myNum2 = nullInt == null ? 0 : nullInt.Value;

_{I changed the response to community wiki to extend and improve}