Welcome to the Lounge

Slacker007 wrote:

it's main purpose is code readability.

void MainMethod() {
   ...
   var methodCall = SomeMethod();
   if (!methodCall.Success) {
     return;
   }
   ...
}

(bool Success, int? ReturnValue) SomeMethod() {
   int? retValue;

   ...
   if (...) {
      return (Success: false, ReturnValue: null);
   }
   ...

   return (Success: true, ReturnValue: retValue):
}

var (Success, ReturnValue) = SomeMethod();
if (!Success) {
    return;
}

private void DoSomething()
{
  var apiEndpoint = new Uri("http://someapi");
  var retryCount = 10;
  var longClassName = new ThisIsAReallyLongNameThatWouldReallyScrewUpTheClassNameDeclaration();
  // body of the method.
}

Pete O'Hanlon wrote:

the idea being that it's easier to scan the name if it lines up.

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.

ZurdoDev wrote:

C#

var url = "<a href="http://someapi">http://someapi</a>";

Is there some benefit to declaring most things var instead of what they actually are? In the case above, a string.

Uri siteUri = new Uri("<a href="http://www.contoso.com/">http://www.contoso.com/</a>");

MadMyche wrote:

But what if you meant it as a URI?

Dim something = "my string"

Mycroft Holmes wrote:

As for var content changing type and not having to refactor