Welcome to the Lounge

class Program
{
    const string _str = "abcdefghijklmnopqrstuvwxyz";

    static void Main(string[] args)
    {
        Foo("A", () => _str.Contains("~"));
        Foo ("B", () => _str.Contains('~'));
        Foo("C", () => _str.IndexOf("~") >= 0);
        Foo("D", () => _str.IndexOf('~') >= 0);
        Foo("E", () => _str.IndexOf("~", StringComparison.Ordinal) >= 0);
    }

    static void Foo(string s, Func<bool> action)
    {
        var sw = new Stopwatch();
        sw.Start();
        for (int i = 0; i < 1000000; i++)
        {
            action();
        }
        sw.Stop();
        Console.WriteLine($"{s} - {sw.Elapsed.Milliseconds}");
    }
}

Mario Vernari wrote:

Typically, I copy the same piece of code two or three times, then I take the last results.

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.

Mario Vernari wrote:

In my experience, the speed measurements at the start of an app are always polluted by the runtime initialization.

Greg Utas wrote:

finally the indecipherable twaddle of E--unless it's some kind of secret code for "Hint: you're looking for a single character and therefore don't have to construct "~"