Is it a version 3.1 issue? Can this be prevented with parentheses? Remember, that && can as well be a (sort of) reference in C++ used for the move semantics feature.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is version 3.1 and I tried parentheses and it fixes the reported "if", so this works:
if ((depX is int) && (depY is int) && (depW is int) && (depH is int))
But on this line:
public bool available => (ProjectDir != null) && (JsonFile != null) && (ProjectFile != null) && (Model != null);
it is still changed to
public bool available => (ProjectDir != null)&& (JsonFile != null)&& (ProjectFile != null)&& (Model != null);
even with parentheses around the entire expression:
public bool available => ((ProjectDir != null)&& (JsonFile != null)&& (ProjectFile != null)&& (Model != null));
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is it a version 3.1 issue? Can this be prevented with parentheses? Remember, that
&&can as well be a (sort of) reference in C++ used for the move semantics feature.This is version 3.1 and I tried parentheses and it fixes the reported "if", so this works:
if ((depX is int) && (depY is int) && (depW is int) && (depH is int))
But on this line:
public bool available => (ProjectDir != null) && (JsonFile != null) && (ProjectFile != null) && (Model != null);
it is still changed to
public bool available => (ProjectDir != null)&& (JsonFile != null)&& (ProjectFile != null)&& (Model != null);
even with parentheses around the entire expression:
public bool available => ((ProjectDir != null)&& (JsonFile != null)&& (ProjectFile != null)&& (Model != null));