"out return" - an even more shortcutty version of "out var"

[ekolis]

Use case:

public static bool ToBool(this string value)
{
	bool.TryParse(value, out return result);
}

versus the existing two line version of this method:

public static bool ToBool(this string value)
{
	bool.TryParse(value, out var result);
	return result;
}

maybe even out could be implied by return?

public static bool ToBool(this string value)
{
	bool.TryParse(value, return result);
}

[CyrusNajmabadi]

This seems like such a short (and rare) coding pattern that it doesn't really need anything to help out here.

Indeed, why not just make it:

public static bool ToBool(this string value)
  => bool.TryParse(value, out var result) && result;

?

[ronnygunawan]

consider this case:

public static bool? ToBoolOrDefault(this string value)
{
    if (!bool.TryParse(value, return result))
    {
        return null;
    }
}

Should the compiler tell you "not all code paths return a value"?

[canton7]

So:

public static bool ToBoolOrDefault(this string value)
  => bool.TryParse(value, out var result) ? result : (bool?)null;