Welcome to the Lounge

string name;
name = "My name is Sander Rossel".Substring(11);
name = "My name is Sander Rossel"[11..];

Exception ex = new Exception();
switch (ex)
{
    case InvalidCastException:
        break;
    case InvalidOperationException:
        break;
    case NullReferenceException:
        break;
    default:
        break;
}

// The alternative is, of course, an if-else statement.
var exType = ex.GetType();
if (exType == typeof(InvalidCastException))
{ }
else if (exType == typeof(InvalidOperationException))
{ }
else
{ }

public (string firstName, string lastName) GetNameParts(string name) { }
// Usage...
(var firstName, var lastName) = GetNameParts("Sander Rossel");
// Or...
var tuple = GetNameParts("Sander Rossel");
Console.WriteLine(tuple.firstName);

Console.WriteLine($"Hi {firstName} {lastName}, welcome to {appName}!");
// vs.
Console.WriteLine(string.Format("Hi {0} {1}, welcome to {2}!", firstName, lastName, appName);

Console.WriteLine("Hello World!"[1..5]);

Console.WriteLine("Hello World!"[..5]);

Rick York wrote:

If I have to stop and think about what some new construct does that is not helpful. I'll take the old, verbose ways that are simple and easy to understand.

M.D.V.

If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.

SeattleC++ wrote:

It all has a purpose.