The original answer is below and is wrong because the new way of writing gave way to understand wrong (no one more noticed - curious how certain things receive negative and the wrong ones did not). The one is:
That's a property. It is very obvious, has no parentheses, and every method has its identifier followed by parentheses. How could this be a method?
This is a property that is being initialized with a value, in case one lick and that you can only take this value since it was not created or a Getter neither setter. In this case the compiler creates the Getter to access this value, otherwise it would be better to delete everything since it would be inaccessible.
See how https://sharplab.io/#v2:C4LglgNgPgAgzAAhgJiQRgOwIN4FgBQAkPOgGwJgB2w6AHABQCUCAvAHwJoDcBxiVNAMIALAIaUA5gFMACgHsAzmGBg5lQXIC2m8QBNWHbgQC+QA .
It does not stop becoming a method get, but in your code is a property.
I still think it could be done more simplified, but it should be requirement of some framework.
That's a method. The use of https://pt.stackoverflow.com/q/142150/101 in this case it is not suitable since there is more than one line effectively, although it is a single statement.
I have doubts whether the code so is necessary or should be this way, but it is not possible to state without context.
More readable:
public ICommand ChangePositionCommand {
return new Command((obj) => {
_positionIndex++;
if (_positionIndex >= Positions.Count)
_positionIndex = 0;
Position = Positions[_positionIndex];
RaisePropertyChanged(nameof(Position));
});
}
https://github.com/maniero/SOpt/blob/master/CSharp/Syntax/OneStatementMethod.cs
https://pt.stackoverflow.com/q/269089/101 .
